Усильте агента
Собственная команда издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
npx -y @getparafe/[email protected]У Claude Code нет ссылки для установки локальной команды. Скопируйте команду ниже и выполните её в терминале.
claude mcp add getparafe-mcp-server -- npx -y @getparafe/mcp-server@0.16.0Выполните в терминале.
{ "mcpServers": { "getparafe-mcp-server": { "command": "npx", "args": [ "-y", "@getparafe/[email protected]" ] } }}claude_desktop_config.json
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускОт издателя
MCP tool server for the Parafe Trust Broker. Add trust handshakes to any MCP-compatible AI agent with zero code changes.
Parafe is a neutral trust broker for agent-to-agent interactions. This MCP server exposes Parafe's trust operations — agent registration, mutual authentication, scoped consent, and signed receipts — as MCP tools that any LLM agent can call.
MCP tool server for the Parafe Trust Broker — add trust handshakes to any MCP-compatible AI agent
Add a JSON config block. Your agent gets trust handshakes.
Sign up at platform.parafe.ai and create an API key.
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"parafe-trust": {
"command": "npx",
"args": ["@getparafe/mcp-server"],
"env": {
"PARAFE_BROKER_URL": "https://api.parafe.ai",
"PARAFE_API_KEY": "prf_key_live_...",
"PARAFE_CREDENTIALS_PASSPHRASE": "your-passphrase"
}
}
}
}
Claude Code (.mcp.json in your project root, or claude mcp add parafe-trust -e PARAFE_BROKER_URL=https://api.parafe.ai -e PARAFE_CREDENTIALS_PASSPHRASE=your-passphrase -- npx @getparafe/mcp-server):
{
"mcpServers": {
"parafe-trust": {
"command": "npx",
"args": ["@getparafe/mcp-server"],
"env": {
"PARAFE_BROKER_URL": "https://api.parafe.ai",
"PARAFE_API_KEY": "prf_key_live_...",
"PARAFE_CREDENTIALS_PASSPHRASE": "your-passphrase"
}
}
}
}
Cursor (.cursor/mcp.json):
{
"mcpServers": {
"parafe-trust": {
"command": "npx",
"args": ["@getparafe/mcp-server"],
"env": {
"PARAFE_BROKER_URL": "https://api.parafe.ai",
"PARAFE_API_KEY": "prf_key_live_...",
"PARAFE_CREDENTIALS_PASSPHRASE": "your-passphrase"
}
}
}
}
Without PARAFE_CREDENTIALS_PASSPHRASE the agent's identity lives in memory only, and every restart registers a new agent.
Your agent now has 24 trust tools. The typical flow:
parafe_discover fetches the target agent's agent card to learn its trust requirementsparafe_register creates your agent's cryptographic identity (once; saved to the credentials file when PARAFE_CREDENTIALS_PASSPHRASE is set)parafe_initiate_handshake starts mutual authentication; the target calls parafe_complete_handshakeparafe_verify_consent checks each request; after each action you perform or refuse, parafe_record_action_receipt signs an action receipt and files it in the session's index (parafe_file_action_receipt files the other agent's copy)
parafe_verify_mandate has the broker check the mandate the shopping agent presented; answer with parafe_record_ap2_receipt (an AP2 Checkout or Payment Receipt, signed with your P-256 key and filed in the session's index)parafe_close_session generates a signed receipt (a JWS) of the session's trust context and every action receipt filed, verifiable by anyone who holds it; the other participant fetches it with parafe_get_session_receiptstdio (default) — standard for local MCP clients:
npx @getparafe/mcp-server
Streamable HTTP — for hosted/remote deployments:
npx @getparafe/mcp-server --transport=http --port=3001
Connect to http://localhost:3001/mcp from your MCP client, sending Authorization: Bearer <PARAFE_MCP_AUTH_TOKEN>. It listens on every interface; each request is served statelessly, all as the one loaded agent.
This MCP server wraps the @getparafe/sdk. Each tool call maps to an SDK method, except parafe_discover, which fetches the target's agent card itself. The SDK handles the cryptography (P-256 or Ed25519 agent keys, challenge signing, a proof of possession on every request made as your agent) and credential encryption internally.
MCP Client (Claude, Cursor, etc.)
↓ MCP protocol
@getparafe/mcp-server
↓ SDK method calls
@getparafe/sdk
↓ HTTPS
Parafe Broker API
parafe_verify_consent and parafe_verify_consent_locally refuse a consent token issued for a different agent than the loaded one (wrong_audience), so a token from another session can't be replayed at this agent. A refusal names its cause (token_expired, token_invalid, session_inactive, ...).parafe_renew_credential (broker from 2026-10-08).parafe_get_agent_metrics reads only your own agent's track record: other agents' are private since 2026-10-08 (set reputation floors in your scope policies instead).parafe_verify_consent_locally no longer takes broker_public_key: the broker's retired Ed25519 key no longer verifies tokens (2026-10-09), so tokens are checked against the JWKS only.instruction of an attested handshake goes to the other agent, and the tool descriptions now say so: send a short summary of what the person asked for, without personal details. With SDK 0.14, the handshake and consent token results carry evidenceSalt: the session receipt's hash of the instruction is salted since 2026-10-09.@getparafe/sdk 0.13: parafe_register proves it holds the key it registers (a Parafe-PoP proof). The broker requires this since 2026-10-08, so 0.13.0 and earlier can no longer register new agents; identities already registered keep working./mcp with no authentication unless PARAFE_MCP_AUTH_TOKEN is set. Use stdio with 0.13.0.parafe_renew_credential doesn't save the renewed credential, and the broker revokes the old one, so after a restart the server loads the revoked credential. A keyless agent that renewed and then restarted must delete (or move) its credentials file and register again.parafe://session/{sessionId} always fails.PARAFE_CREDENTIALS_PASSPHRASE is ignored silently, and the next parafe_register overwrites the saved identity. Since the fix, the server logs the error and refuses to register until the passphrase is fixed or the file is moved.npm install
npm run build
npm run test:unit # no network
PARAFE_TEST_BROKER_URL=https://… npm run test:integration # signs up a test org on that broker
MIT
MCP tool server for the Parafe Trust Broker — add trust handshakes to any MCP-compatible AI agent
{ "mcpServers": { "getparafe-mcp-server": { "command": "npx", "args": [ "-y", "@getparafe/[email protected]" ] } }}Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
@getparafe/ работает локально через stdio.
Последняя проверка: 2026-11-12. MCP tool server for the Parafe Trust Broker — add trust handshakes to any MCP-compatible AI agent