What It Does
- Input: A single agent endpoint URL
- Assessment: Runs the
mcp-agent-assessmentpipeline with protocol-specific validators - Output: Unified verdicts per protocol layer plus raw assessment data
Protocol Layers
AgentProbe assesses eight protocol layers:| Layer | What it checks |
|---|---|
| HTTP | Connectivity, HTTPS, SSL validation, CORS, HTTP/2 detection |
| MCP | Server discovery, tool/resource/prompt listing, capability detection |
| A2A / AP2 | Agent card validation, AP2 version and role detection via capabilities.extensions and X-A2A-Extensions header |
| x402 | Payment-required endpoint detection with scheme, network, and token analysis |
| OAuth | Authorization server metadata discovery |
| MCP Apps | UI resource detection for MCP applications |
| HTML | Website detection, Content-Type, SSL status, HTTP/2 |
| ERC-8004 | On-chain agent registry lookup with OASF classification, reputation, and metadata extraction |
Not every endpoint supports all protocols. AgentProbe gracefully handles unsupported layers and shows results only for detected protocols.
Architecture
API Endpoints
POST /api/validate
Returns a structured validation result with separate sections for each protocol.
mcp, a2a, ui (MCP Apps), and oauth objects, each with status, categories, summary, and messages.
POST /api/assess
Returns the raw assessment result from mcp-agent-assessment with full layer details.
| Key | Type | Description |
|---|---|---|
timeout | number | Timeout in milliseconds |
erc8004 | object | ERC-8004 config with rpcNodes |
POST /api/lookup
Query the ERC-8004 on-chain registry for agent registration data, endpoints, OASF classification, and reputation.
| Key | Type | Description | Required |
|---|---|---|---|
agentId | number | Agent token ID in the ERC-8004 registry | Yes |
chainId | number or string | Chain ID (e.g., 8453 for Base) or CAIP-2 (e.g., eip155:8453) | Yes |
rpcNodes | object | Custom RPC nodes per chain alias | No |
Validate Your Own MCP Server
Deploy your MCP server
Make sure your MCP server is publicly accessible (e.g., via ngrok or a cloud deployment).
Open AgentProbe
Go to agentprobe.xyz in your browser.
Enter your endpoint URL
Paste your MCP server URL (e.g.,
https://your-server.example.com/mcp) and click validate.Authentication
Authentication is optional. WhenAPI_TOKEN is not set, the API is open (dev mode).
When API_TOKEN is set, two authentication methods are supported:
| Method | How it works |
|---|---|
| Session Cookie | Browser visits the UI and receives a session cookie automatically |
| Bearer Token | External scripts send Authorization: Bearer <API_TOKEN> header |
Dependencies
AgentProbe builds on the FlowMCP validator ecosystem:| Package | Purpose |
|---|---|
| mcp-agent-assessment | Unified assessment pipeline |
| a2a-agent-validator | A2A agent card and AP2 detection |
| x402-mcp-validator | x402 payment protocol validation |
| mcp-apps-validator | MCP Apps UI resource detection |
| erc8004-registry-parser | ERC-8004 on-chain registry parsing |
Links
- Live Demo: agentprobe.xyz
- GitHub: FlowMCP/mcp-agent-validator
- Video: Watch on YouTube
- DoraHacks: dorahacks.io/buidl/39293