_ registry / mcp streamable-http · checked 3h ago

multilo

https://www.multilo.com

Registry code: a30eaad768441837

api record

Multilo is an AI-native document IWE (Integrated Writing Environment) for academic research and writing — a desktop app that does for research papers, essays and theses what an IDE does for code. Use search_docs to find how a feature works, get_page to read any public page as clean Markdown, and list_updates for what shipped recently.

endpoint
https://www.multilo.com/api/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 multilo live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is multilo free to use?
Yes — the hub reached it with no key and no payment.
What tools does multilo have?
3 tools: list_updates, search_docs, get_page.
Is multilo 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
99.1%

90 days 99.1%· all time 99.1%

latency
1,099ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 117 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search product documentation
  • read a public page as markdown
  • list recent changelog entries
takes → gives
text → text
tools
3 reads
note
documentation mirror
_ 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

_ what it can do 3 tools
2 open 1 never probed 2 of 3 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.

  • search_docs reads open 15h ago

    Search the Multilo product documentation by keyword. Returns matching pages with a one-line summary, the human URL, and a clean-Markdown URL suitable for fetching the full page. Use this first when asked how a Multilo feature works.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Maximum results to return (1-25). Defaults to 10."
    },
    "query": {
      "type": "string",
      "description": "Keywords, e.g. 'citation verification' or 'export docx'."
    }
  }
}
    arguments 16 lines
  • get_page reads open 15h ago

    Fetch any public Multilo page as clean Markdown — documentation, pricing, comparisons, blog posts, or the homepage. Accepts a path ('/pricing', '/docs/install/download') or a full multilo.com URL. Far cheaper and cleaner than fetching the HTML.

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Site path or full multilo.com URL, e.g. '/pricing' or '/docs/install/download'."
    }
  }
}
    arguments 12 lines
  • list_updates reads unknown never probed

    List the most recent Multilo changelog entries — shipped features, improvements and fixes, newest first. Use when asked what is new, whether something has shipped, or how recently the product changed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many updates to return (1-50). Defaults to 10."
    }
  }
}
    arguments 9 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 a30eaad768441837.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a30eaad768441837/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/a30eaad768441837/badge.svg)](https://brick.blue/agent/a30eaad768441837?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
70%

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.