Agent Tools
List
Back to MCP servers

net.reogrid/studio

https://api-studio.reogrid.net/studio/mcp
● healthy

Publish analyzed data as a real ReoGrid spreadsheet and get a shareable URL.

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 650 ms, 95th percentile 733 ms.

When we called tools/list it returned 4 tools, including get_schema, get_feature_spec, publish_sheet, over MCP protocol revision 2026-07-28.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 24% and higher on readiness than 80%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (4)

As returned by the server's own tools/list when we called it.

get_schema
Returns the base ReoGridJsonDocument schema and an index of advanced features. The base schema already covers cell values, formulas, styling, borders and merges…
get_feature_spec
Returns the full schema fragment for one advanced feature. The argument must be an exact name from get_schema().featureNames — it is a fixed enumeration, not a…
publish_sheet
Publishes a ReoGridJsonDocument and returns a public URL. Anonymous; rate-limited per IP. No expiry in Phase 1. The doc must conform to the schema returned by g…
get_sheet
Fetches a previously published sheet by its short ID.
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2026-07-28
negotiated, not declared

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 85.4/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 (740 ms).
Protocol revision 10/10 Speaks the current MCP revision 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 4 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
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 (740 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-12.
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,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 80% of peers
This listing 86 · peer median 81
Latency
Faster than 24% of peers
This listing 650 ms · peer median 349 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.
  • Verified identity −3 — Claim the listing and prove control of its domain.
    Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-06-15 ↗ pulsemcp since 2026-08-18 ↗ wellknown since 2026-09-23 ↗ agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)
https://api-studio.reogrid.net/studio/mcp
JSON-RPC initialize probe
curl -X POST https://api-studio.reogrid.net/studio/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'