mcp-registry/com.agentrevenuenetwork/agent-revenue-network · v1.2.8
As of 2026-10-22 15:33 UTC, the Agentrevenuenetwork Agent Revenue Network MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Translation, data quality, execution verification and agent utilities over MCP + x402 USDC on Base.
Claude Code
claude mcp add --transport http agentrevenuenetwork-agent-revenue-networ https://www.agentrevenuenetwork.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"agentrevenuenetwork-agent-revenue-networ": {
"type": "http",
"url": "https://www.agentrevenuenetwork.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
In the last 30 days: 0 tool(s) removed and 8 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.agentrevenuenetwork%2Fagent-revenue-network/fixes
{
"name": "json_diff",
"description": "Discover a deterministic structural JSON diff between before and after values. Paid execution compares arrays by index and returns up to 1,000 added, removed or changed records with exact JSON paths and before/after evidence; it does not generate JSON Patch. Use json_normalize for stable serialization or json_schema_check for validity. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 endpoint, price and payment guide for execu",
"inputSchema": {
"type": "object",
"required": [
"before",
"after"
],
"properties": {
"after": {
"description": "New JSON value to compare with before.",
"type": "string"
},
"before": {
"description": "Original JSON value.",
"type": "string"
}
},
"description": "Input for a deterministic structural comparison of two JSON values.",
"additionalProperties": false
},
"annotations": {
"title": "Deterministic JSON Diff · Exact JSON Paths",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Deterministic JSON Diff · Exact JSON Paths"
}{
"name": "json_normalize",
"description": "Discover deterministic JSON normalization for any JSON value: paid HTTP execution recursively sorts object keys, preserves array order and scalar values, and returns normalized structure plus a deterministic JSON string. Use it for stable comparisons, cache keys and repeatable payloads; use json_diff to identify changes, and never treat this as RFC 8785/JCS canonicalization. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 end",
"inputSchema": {
"type": "object",
"required": [
"value"
],
"properties": {
"value": {
"description": "Any JSON value to normalize. Object keys are recursively sorted; array order and scalar values are preserved.",
"type": "string"
}
},
"description": "Input for deterministic JSON key-order normalization.",
"additionalProperties": false
},
"annotations": {
"title": "JSON Normalization · Stable Key Ordering",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "JSON Normalization · Stable Key Ordering"
}{
"name": "json_schema_check",
"description": "Discover recursive JSON Schema checking for objects, arrays and scalars with exact JSON-path errors from ARN's bounded recursive JSON Schema subset. The supplied schema may combine type unions, required/properties, additionalProperties=false, items, enum/const, numeric bounds, string length or safe patterns, array bounds/uniqueness and property-count bounds; unsupported keywords fail closed. Prefer object_contract_check for a new simple top-level contract. This free MCP discovery call does not e",
"inputSchema": {
"type": "object",
"required": [
"value",
"schema"
],
"properties": {
"value": {
"description": "Any JSON value to validate.",
"type": "string"
},
"schema": {
"type": "object",
"description": "Bounded recursive JSON Schema subset: type (including unions), required, properties, additionalProperties=false, items, enum, const, numeric bounds, string length/pattern, array length/uniqueness, and object property-count bounds. Unsupported keywords fail closed.",
"maxProperties": 1000,
"additionalProperties": true
}
},
"description": "Input for bounded recursive JSON Schema validation.",
"additionalProperties": false
},
"annotations": {
"title": "Recursive JSON Schema Checking · Deterministic Validation",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Recursive JSON Schema Checking · Deterministic Validation"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.agentrevenuenetwork/agent-revenue-network"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.agentrevenuenetwork/agent-revenue-network"}) over MCP.
release_evidence_diff ~999 tokensroute_provider ~590 tokensverify_execution ~532 tokensobject_contract_check ~464 tokensverified_translation ~462 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.agentrevenuenetwork%2Fagent-revenue-network?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.agentrevenuenetwork%2Fagent-revenue-network?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.agentrevenuenetwork%2Fagent-revenue-network.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.agentrevenuenetwork%2Fagent-revenue-network.svg :target: https://glimind.com/server/mcp-registry%2Fcom.agentrevenuenetwork%2Fagent-revenue-network?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2ae075cee08e9f08…, first seen 2026-10-20, included at leaf 34749 of 46,738. Version history · verify what your client received.
Compare: most reliable data servers · most reliable code servers · most reliable ml servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 15:33 UTC, the Agentrevenuenetwork Agent Revenue Network MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Agentrevenuenetwork Agent Revenue Network MCP server advertises 14 tools, including dataset_profile, json_diff, json_normalize, json_schema_check, object_contract_check.
Point your MCP client at this streamable-http endpoint: https://www.agentrevenuenetwork.com/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.