@yantrix/mcp
Dynamic MCP server for the Yantrix API portfolio. One install gives any MCP-compatible AI agent access to 30+ tools across research, memory, language, legal, security, intelligence, and more.
What makes it dynamic
Unlike static MCP packages, @yantrix/mcp fetches its tool list from registry.yantrix.ai on startup. When new APIs are added to the Yantrix portfolio, they appear automatically on your next MCP host restart — no package update needed.
Install
npm install -g @yantrix/mcpOr use directly with npx:
npx @yantrix/mcpConfiguration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"yantrix": {
"command": "npx",
"args": ["@yantrix/mcp"],
"env": {
"X_PAYMENT_HEADER": "<your-x402-payment-proof>",
"DEV_MODE": "false"
}
}
}
}Development / Testing (no payment required)
{
"mcpServers": {
"yantrix": {
"command": "npx",
"args": ["@yantrix/mcp"],
"env": {
"DEV_MODE": "true"
}
}
}
}Environment Variables
Variable | Description | Default |
| x402 payment proof for USDC micropayments | — |
| Skip payment validation (local testing only) |
|
| Custom registry URL |
|
Available Tools
Tools are loaded dynamically from the registry. Current categories:
Category | Tools |
| verify_claim, deep_verify_claim, batch_verify |
| write_memory, read_memory, search_memory |
| transliterate, indic_sentiment, detect_code_switching, indic_ner |
| scan_contract, scan_clause |
| model_threats, check_compliance |
| score_trend, compare_trends, scan_competitor |
| generate_exam |
| rewrite_in_style |
| company_lookup, gst_intelligence, lookup_ifsc |
| analyze_call, extract_crm_data |
| validate_phone, detect_timezone, convert_timezone, find_timezone_overlap |
| check_quota, consume_quota, track_api_event |
| argue_claim, detect_fallacies |
Payment
All tools use x402 micropayments in USDC on Base Mainnet.
Costs range from $0.0001 (event tracking) to $0.025 (sales call analysis).
To get a payment header, visit x402.org or use the x402 client SDK.
How it works
1. npx @yantrix/mcp starts
2. Fetches https://registry.yantrix.ai/mcp-registry.json
3. Registers all tools dynamically
4. MCP host calls any tool
5. @yantrix/mcp routes call to correct Yantrix API
6. Response returned to agentThe registry is cached for 5 minutes. New tools appear on next restart.
Adding new APIs (for maintainers)
No npm republish needed. Just update main.py in the mcp-registry service:
# Add to TOOLS list in mcp-registry/main.py
{
"name": "new_tool_name",
"service": "newapi",
"endpoint": "https://newapi.yantrix.ai/endpoint",
"method": "POST",
"description": "What this tool does.",
"input_schema": {...},
"cost_usdc": "0.005",
"category": "category",
}Deploy the registry → all users get the new tool on next restart.
Links
Registry: https://registry.yantrix.ai
Docs: https://yantrix.ai
x402: https://x402.org