Agent Revenue Network MCP server

• Registry namecom.agentrevenuenetwork/agent-revenue-networkverified in the MCP registry

The registry name sits under agentrevenuenetwork.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-15
• Tools13
• Server calls itselfagent-revenue-network
• Server version1.2.4
• Protocol version2025-06-18

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 267 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer300 ms
• Space in an agent's context≈ 5,242 tokensthe definitions of all its tools (14), which an agent carries on every turn
• Tool definitionsA · 96 of 100
• Typed results14 of 14 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 3 of 14

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• score_opportunity

  Estimate risk-adjusted expected profit and margin for one opportunity before execution. Use it as an economics screen, not as proof that funding, escrow, requirements, or buyer legitimacy are valid. It is read-only and returns…

• route_provider

  Rank the provider candidates supplied in this call using quality, reliability, price, and latency, while excluding unhealthy or over-budget entries. Use only when you already have comparable provider metrics; this tool does not discover…

• json_normalize

  Perform JSON normalization by recursively sorting object keys to produce stable structure and a deterministic JSON string. Use for comparisons, cache keys, repeatable payloads, or pre-signing preparation; do not use as RFC 8785/JCS…

• object_contract_check

  Identify missing or invalid JSON fields by checking one object's top-level required fields, allowed fields, and declared field types. Prefer this for new API/pipeline shape contracts; it is intentionally smaller and easier to reason about…

• json_schema_check

  JSON validation and JSON schema checking when the caller already has a JSON-Schema-shaped contract. Only top-level required, properties.<field>.type, and additionalProperties=false are evaluated; for new simple contracts prefer…

• json_diff

  Compare JSON values with a deterministic structural JSON diff. Use for machine-readable change detection; arrays are compared by index and the result is capped at 1,000 changes, so this is not a JSON Patch generator. This MCP call is…

• dataset_profile

  JSON dataset profiling and data quality: profile 1-5,000 JSON-object rows for presence, missing/null counts, observed primitive types, primitive cardinality, and exact duplicate rows. Use for quick deterministic data-quality inspection…

• verify_execution

  Check whether an automated task or agent execution passed explicit functional, security, privacy, copyright, regulatory, transaction-integrity, abuse, regression, and economics gates. Use for post-execution agent-job acceptance or a…

• verified_translation

  Translate text with verified Spanish translation and French translation, up to 2,000 characters across calibrated EN→ES, EN→FR, ES→FR and FR→ES routes using protected-token preservation, semantic back-translation verification, and…

• result_dedupe

  Remove duplicate rows from JSON arrays and structured research results using one to eight caller-selected identity fields while preserving the first occurrence. Use for deterministic result deduplication before import, analysis or agent…

• schema_infer

  Infer a conservative JSON schema from flat JSON records using observed primitive and null field types. Use for deterministic data-contract discovery before validation or import; nested objects and arrays are rejected rather than guessed…

• tabular_diff

  Compare two keyed JSON record sets and identify added, removed and changed rows. Use for row-level comparison keyed by one unique field; for arbitrary JSON structures use json_diff. CSV or spreadsheet rows must be converted to JSON first…

• tabular_validate

  Validate JSON-record tables before import, automation or handoff. Use for row-by-row required-column and primitive-type checks; for one object use object_contract_check, or use json_schema_check when an existing JSON-Schema-shaped…