_ registry / mcp streamable-http · checked 50m ago

cybermax-ledgermoor

https://gpt-ledgermoor.cybermaxtools.com

Registry code: efc7c1e453f9998e

api record

Ledgermoor Table to Excel: Any table to Excel or CSV. table_to_excel: Make an Excel or CSV file from a table. Results include an "about" link to the product page.

endpoint
https://gpt-ledgermoor.cybermaxtools.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cybermax-ledgermoor live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is cybermax-ledgermoor free to use?
Yes — the hub reached it with no key and no payment.
What tools does cybermax-ledgermoor have?
1 tool: table_to_excel.
Is cybermax-ledgermoor safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
63ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • table_to_excel unknown 50m ago

    Use this when the user wants a table turned into an Excel spreadsheet (.xlsx) or a CSV file: "convert this PDF table to Excel", "make this into a spreadsheet", "export to CSV", "PDF to Excel", "screenshot to Excel". First read the table yourself from the uploaded file, image or text, then pass the header row and every data row exactly as written (keep currency signs and minus signs; do not total or reorder). Returns download links for .xlsx and .csv and a preview.

    mcp-tool

    {
  "type": "object",
  "required": [
    "rows"
  ],
  "properties": {
    "rows": {
      "type": "array",
      "items": {
        "type": "array",
        "items": {
          "type": [
            "string",
            "number",
            "null"
          ]
        }
      },
      "maxItems": 1000,
      "minItems": 1,
      "description": "Data rows, each an array of cell values in column order"
    },
    "title": {
      "type": "string",
      "description": "What the table is, e.g. \"March bank transactions\" (used for the file name)"
    },
    "headers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Column names (the header row)"
    },
    "sheetName": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id efc7c1e453f9998e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/efc7c1e453f9998e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/efc7c1e453f9998e/badge.svg)](https://brick.blue/agent/efc7c1e453f9998e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on cybermaxtools.com 24 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

16 more sit on this domain. All of them.