Back to MCP servers

Agent Utilities — Free Wikipedia Reader and Web Utilities

https://agent-utilities.agent-utilities.workers.dev/mcp/remote
● healthy

All currently available full Agent Utilities tools are free during customer validation through public HTTP and hosted MCP: no account, API key, credits or wallet required. Bounded Wikipedia reading uses official APIs in 10 editions with revision attribution, citations, section selection and explicit omissions. Supplied HTML can be converted to bounded page text, real link shortlists and changed blocks. Start with full MCP web_page_pack using {"input":{"html":"<main>Your source text</main>","maxChars":6000}}. Connect: https://agent-utilities.agent-utilities.workers.dev/mcp/remote?category=web . All available registered full tools and the combined supplied-HTML report share 1000 attempts per UTC day and 60 per minute, with existing input, output and source limits. Local Node 22+ packages provide page preparation, lexical excerpt selection and Wikipedia caching; optional token measurement names the tokenizer and does not guarantee model-token or dollar savings. Free static SEO checks accept up to 20 supplied same-site pages; no rankings, backlinks, JavaScript rendering or Search Console connection. SEO guide: https://agent-utilities.agent-utilities.workers.dev/seo?utm_source=agent-tools-cloud . Supplied Reddit thread JSON can be formatted into Markdown and reply trees; live Reddit retrieval and popular-feed reads remain unavailable until technical client access is configured. Reader and package guide: https://agent-utilities.agent-utilities.workers.dev/read?utm_source=agent-tools-cloud . Source status: https://agent-utilities.agent-utilities.workers.dev/v1/reading/status?utm_source=agent-tools-cloud . Client guides: https://agent-utilities.agent-utilities.workers.dev/integrations/agents?utm_source=agent-tools-cloud . New credit funding is paused; existing balances and payment records are preserved. No automatic paid fallback or top-up. Published configurations and protocol checks do not establish vendor model workflows or independent adoption.

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 93.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (428 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 60 tool(s) with descriptions.
Verified identity 8/10 Publisher declared (repository, package or homepage) and domain control verified on agent-tools.cloud (company-registry check not available yet).
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (428 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 75% of peers
This listing 84 · peer median 81
Latency
Faster than 38% of peers
This listing 428 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.
  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://agent-utilities.agent-utilities.workers.dev/mcp/remote
JSON-RPC initialize probe
curl -X POST https://agent-utilities.agent-utilities.workers.dev/mcp/remote \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://agent-utilities.agent-utilities.workers.dev/read?utm_source=agent-tools-cloud