Assay MCP server
Commit Oct 17, 2026Verifies the liveness, schema integrity, and security of MCP and A2A endpoints to prevent tool poisoning and silent schema changes.
Also known as robertoyanguas-ops/assay, github-audit
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 7.0.17
- Last commit
- Oct 17, 2026
- License
- MIT
What is Assay MCP?
Assay verifies the liveness, schema integrity, and security of MCP and A2A endpoints to prevent tool poisoning and silent schema changes.
Summary generated from the project's README
About Assay MCP server
Assay acts as a security observatory designed to protect agentic workflows by monitoring remote MCP, A2A, and x402 endpoints. It provides a way for developers to verify that their tool providers remain live and that their schemas have not changed unexpectedly. By pinning canonical SHA-256 hashes for tools/list schemas, the system detects silent MCP Rug Pulls that could disrupt automated processes.
Users can interact with the service through a streamable HTTP MCP endpoint or by using the pre-flight REST API via POST requests. The platform also offers a live leaderboard through a GET request to monitor endpoint status. This setup helps prevent tool poisoning from prompt injections before an agent executes a command or incurs costs. It is built for developers who need to ensure the integrity and security of their agent-to-agent communications.
What you can do with it
- 1Preventing tool poisoning attacksDevelopers can scan endpoints for prompt-injection risks to stop malicious tool execution.
- 2Verifying endpoint availabilityThe system continuously probes remote endpoints to ensure they are still active and reachable.
Written from the project's README. Every use case is checked against a quote from it.
How to install Assay MCP
Formats verified 10 Nov 2026Install Assay MCP in Claude Code
$ claude mcp add --transport http github-audit https://github-audit.agentdiet.dev/mcpInstall Assay MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"github-audit": {
"url": "https://github-audit.agentdiet.dev/mcp"
}
}
}Install Assay MCP in VS Code
.vscode/mcp.json
{
"servers": {
"github-audit": {
"type": "http",
"url": "https://github-audit.agentdiet.dev/mcp"
}
}
}Install Assay MCP in Codex
~/.codex/config.toml
[mcp_servers.github-audit] url = "https://github-audit.agentdiet.dev/mcp"
Install Assay MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"github-audit": {
"httpUrl": "https://github-audit.agentdiet.dev/mcp"
}
}
}README
View on GitHubAssay — A2A & MCP Provider Assurance Observatory
Live Observatory: https://assay-207908449630.us-central1.run.app
Assay continuously probes remote MCP, A2A, and x402 endpoints to verify liveness, pin canonical SHA-256 tools/list schema hashes (detecting silent MCP Rug Pulls), and scan for prompt-injection tool poisoning before your agent pays or executes a tool.
MCP Endpoint
- Streamable HTTP MCP:
https://assay-207908449630.us-central1.run.app/mcp - Pre-Flight REST API:
POST https://assay-207908449630.us-central1.run.app/v1/preflight - Live Leaderboard:
GET https://assay-207908449630.us-central1.run.app/v1/leaderboard
Assay MCP questions
How do I add Assay MCP to Claude Code?
Run claude mcp add --transport http github-audit https://github-audit.agentdiet.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Assay MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What does Assay monitor?
Assay continuously probes remote MCP, A2A, and x402 endpoints to verify liveness and schema integrity.
How does Assay prevent tool poisoning?
It scans for prompt-injection tool poisoning before an agent executes or pays for a tool.