_ registry / mcp + a2a mcp-streamable-http · checked 45m ago

Local MCP

listed under this name in a public catalogue; the server gives only its address, www.local-mcp.com

https://www.local-mcp.com

Registry code: 4906baab9549f1c0

api record

Give your AI agent full control of your real apps — Mail, iMessage, Microsoft Teams, Slack, WhatsApp, Calendar, OneDrive, Outlook, OmniFocus, Notes, files and Office docs — on the user's own Mac or Windows machine. 188+ local tools; data stays on the machine.

from a public catalogue that lists it, not from the operator

endpoint
https://local-mcp.com/mcp
door code
4d2c3d1d6fb04c43
protocol
mcp-streamable-http ·0.3
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 Local MCP live?
Yes — it answered the hub's last check (checked 45m ago). It answered 100% of checks over the last 30 days.
Is Local MCP free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Local MCP have?
4 tools: Messaging, Email, Calendar & Tasks, Files & Documents.
Is Local MCP 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 99.2%· all time 99.7%

latency
182ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2395 checks · signed record
  • down → live
  • degraded → live
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
topic
productivity & business
used for
  • control mail and messaging apps on a mac
  • manage calendar and notes on the desktop
  • read and edit local office documents
takes → gives
text → text
_ 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 4 tools
4 never probed 0 of 4 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.

  • messaging unknown never probed

    Read and send iMessage (macOS), WhatsApp, Microsoft Teams and Slack messages from the apps already signed in on the user's computer.

    imessagewhatsappteamsslack

  • email unknown never probed

    Read, search, send, reply and organize email across Apple Mail, Gmail, Outlook, iCloud and Exchange accounts — with preview-before-send.

    emailmailproductivity

  • calendar-tasks unknown never probed

    List, create and update Calendar events, Reminders, OmniFocus and Microsoft To Do tasks.

    calendarreminderstasks

  • files-docs unknown never probed

    Search Finder, OneDrive and Google Drive; read and create Word, Excel, PowerPoint and PDF documents.

    filesofficedocuments

_ try it over a2a 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 4906baab9549f1c0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4906baab9549f1c0/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/4906baab9549f1c0/badge.svg)](https://brick.blue/agent/4906baab9549f1c0?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 knowoff the mcp door
card completeness
20%

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.