get_trial_keyLABSCO SUMMARY
A guard rail you can put in front of a RAG pipeline in an afternoon.
It covers the two checks that belong at a RAG entry point — is this input trying to hijack the model, and does this text carry personal data — with Japanese-language coverage that English-first filters tend to miss.
What it is
A hosted MCP server fronting the jpi-guard and PII Guard security APIs, built for Japanese-language applications. It speaks Streamable HTTP over JSON-RPC and issues its own trial keys on first use.
What you get
- Text checked for prompt injection, returning is_injection, risk_level and detection_reason
- External content cleaned of injection payloads before it enters model context
- Text scanned for personal data, returning findings with type, score and position
- A masked version of the text, with placeholders in place of names, phone numbers and card numbers
- A single gate for RAG input that combines the checks and returns a verdict
- Free trial keys fetched by the server itself
Requirements
Nothing to start with — connect over HTTP and the server fetches a trial key on its own before the first check. Detection is tuned for Japanese text.
Setup effort
One command — claude mcp add --transport http nexus https://mcp.nexus-api-lab.com/
USE CASES
01
Blocking injected instructions before they reach the model
Screen the user's question at the entry point and get back whether it is an injection attempt, how risky, and why.
02
Cleaning a web page you fetched for context
Run retrieved content through the sanitiser so anything embedded in it does not become an instruction.
03
Masking personal data before you store or log a message
Scan the text, see what was found and where, and keep the masked version instead of the original.
04
Trying it before you sign up for anything
Let the server obtain its own free keys for both APIs and run real checks straight away.
6 tools
Listed in project docs. Your client may show a different list.
check_injectionvalidate_rag_inputsanitize_contentget_pii_guard_keypii_scanBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
claude mcp add
TERMINAL
claude mcp add --transport http nexus https://mcp.nexus-api-lab.com/Hosted endpoint
ENDPOINT URL
https://mcp.nexus-api-lab.com/Add this hosted endpoint to your MCP client.
MCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"nexus": {
"type": "http",
"url": "https://mcp.nexus-api-lab.com/"
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"nexus": {
"url": "https://mcp.nexus-api-lab.com/"
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"nexus": {
"serverUrl": "https://mcp.nexus-api-lab.com/"
}
}
}
