mu.micro/mu
REMOTE · MICRO.MU
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Available components
Last scanned (5 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Recent critical change
Authorization (20 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (alerts_update). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 12582 tokens (~74/item across 170 items; 170 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety95
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 12 of 15 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "blog_create" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 170 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 0
- New tool “alerts_update”, which the server declares destructive security
- New tool “alerts_list” functional
- New tool “alerts_raise” functional
- 22 Oct 26 +1
- Judged manipulation: unverified → pass ▲ security
- “groups_create” added an optional parameter “description” cosmetic
- “groups_update” reworded the description of “action” cosmetic
- “groups_update” reworded the description of “value” cosmetic
- 20 Oct 26 +14
- Stability: fail → pass ▲ security
- 14 Oct 26 −14
- Stability: pass → fail ▼ security
- 13 Oct 26 0
- Stability: fail → pass ▲ security
- 10 Oct 26 0
- Stability: pass → fail ▼ security
- 7 Oct 26 −1
- Judged manipulation: pass → unverified ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://micro.mu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=micro.mu | CN=YR2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | RSA 2048 | SHA256-RSA | 558fed297b8fa8136674184dfe454deb606 |
| SANs: micro.mu | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of micro.mu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| mu. | present | 46330, 46579 | 8, 8 | Verified |
| micro.mu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; media-src 'self' data: blob: https:; connect-src 'self'; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; object-src 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://micro.mu/mcp | Verified | 200 | |
| http (plaintext) | http://micro.mu/mcp | HTTPS enforced | 301 | https://micro.mu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
news_headlines Headlines news ~27
Read the home card headlines: latest story per topic, freshest first, at most ten
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
news_list Browse news ~74
Read recent news headlines with short summaries, balanced across topics
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | today to restrict headlines to the caller’s local calendar day |
| limit | number | – | Optional max number of headlines (default 30) |
| topic | string | – | Optional topic/category filter (e.g. tech, world, business) |
No output schema declared.
No examples provided.
news_read Read news ~36
Read one news article in full by its id or URL
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Article id (from Headlines) or article URL |
No output schema declared.
No examples provided.
news_search Search news ~33
Search indexed and live news for a topic
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search terms, e.g. latest AI news |
No output schema declared.
No examples provided.
notes_add Add notes ~76
Write a note under a title, so it is there next conversation. Writing a title that exists rewrites that note
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | What the note says |
| title | string | yes | What the note is called, e.g. "location" or "project brief". Writing a title that exists rewrites that note |
No output schema declared.
No examples provided.
notes_delete Delete notes ~31
Delete one note by title
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | The note to delete, as returned by notes_list |
No output schema declared.
No examples provided.
notes_get Read notes ~46
Read one note by title. Use it when you know the title; notes_list when you do not
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | The note's title, as given to notes_add |
No output schema declared.
No examples provided.
notes_list Browse notes ~20
List every note the caller has written, with its text
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
notify_devices Devices notify ~33
Whether this account can be reached by notification at all, and on which devices. Worth asking before promising to tell somebody something
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
notify_send Send notify ~131
Interrupt yourself on your own devices — a phone, a laptop — with the page closed. For the thing that cannot wait until the next time somebody looks. An answer to a question belongs in the thread it was asked in, not here
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | A second line, up to about 300 characters. Optional |
| title | string | yes | The line on the lock screen. Short — this is the whole message on a watch |
| url | string | – | Where tapping it goes, e.g. /inbox. A notification you cannot act on trains someone to ignore the next one |
No output schema declared.
No examples provided.
places_address Get an email address ~72
Name the place at a latitude and longitude — the reverse of places_geocode. Use it whenever you have coordinates and need to say where that is
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude, e.g. 51.5308 |
| lon | number | yes | Longitude, e.g. -0.1238 |
No output schema declared.
No examples provided.
places_elevation Elevation places ~102
How high a place is above sea level, in metres and feet. Sampled from a 90-metre global elevation model, so a summit reads a little under its surveyed height
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Optional latitude, if the location is already known |
| lon | number | – | Optional longitude, if the location is already known |
| place | string | – | A place name or address, e.g. 'Denver' or 'Ben Nevis' |
No output schema declared.
No examples provided.
places_geocode Geocode places ~32
Resolve a place name or address to coordinates
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | A place name or address to locate |
No output schema declared.
No examples provided.
places_nearby Find nearby places ~124
List points of interest near a location. Each one says whether it is open right now where that is known, so "is anything open near me" is one call
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Optional latitude |
| lon | number | – | Optional longitude |
| near | string | – | Place to look around, e.g. 'Camden, London' (or give lat/lon) |
| query | string | – | Optional keyword to filter by, e.g. 'cafe' |
| radius | number | – | Optional radius in metres (default 1000) |
No output schema declared.
No examples provided.
places_search Search places ~145
Find places by name or category, optionally near a location. Each one says whether it is open right now where that is known, rather than raw opening-hours text to interpret
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Optional latitude, if the location is already known |
| lon | number | – | Optional longitude, if the location is already known |
| near | string | – | Optional place to search near, e.g. 'Shoreditch, London' or 'SF' |
| query | string | yes | What to look for, e.g. 'ramen', 'pharmacy', 'Blue Bottle Coffee' |
| radius | number | – | Optional search radius in metres (default 2000) |
No output schema declared.
No examples provided.
prayer_qibla Qibla for prayer ~50
Get the qibla — the compass bearing to face for Islamic prayer from a location
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude of the location |
| lon | number | yes | Longitude of the location |
No output schema declared.
No examples provided.
prayer_reflection Prayer times for prayer ~36
Get today's Islamic reflection — a verse of the Quran with its surah, a saying of the Prophet, and a name of Allah
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prayer_saying Prayer times for prayer ~53
Look up a hadith from Sahih al-Bukhari, optionally from a given book
| Name | Type | Req | Description |
|---|---|---|---|
| book | number | – | Book number within Sahih al-Bukhari. Omit for a saying from any book |
No output schema declared.
No examples provided.
prayer_search Search prayer ~57
Search the Quran, the hadith and the names of Allah by meaning — ask a question in plain language rather than naming a reference
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A question in plain language, e.g. "what is said about patience" |
No output schema declared.
No examples provided.
prayer_times Prayer times for prayer ~110
Get today's Islamic prayer times (salah) for a location, and which prayer is next
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude of the location |
| lon | number | yes | Longitude of the location |
| method | string | – | Calculation convention: isna, mwl, egypt, karachi, gulf, diyanet, muis or jakim (defaults to isna) |
| tz | string | – | IANA timezone of the location, e.g. Europe/London (defaults to UTC) |
No output schema declared.
No examples provided.
prayer_verse Prayer times for prayer ~76
Look up a chapter of the Quran, or one verse within it, by number. Use prayer_search to ask a question instead of naming a reference
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | number | yes | Chapter (surah) number, 1-114 |
| verse | number | – | Verse number within the chapter. Omit for the whole chapter |
No output schema declared.
No examples provided.
recall_conversation Conversation recall ~60
Read one whole conversation back by id, as recall_search and recall_list report it
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The conversation's id, as recall_search reports it |
| limit | number | – | Max messages, most recent kept (default 50) |
No output schema declared.
No examples provided.
recall_list Browse recall ~60
List the caller's conversations, most recently active first, with what each is about and where it happened
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only conversations on one client: web, mail, cli |
| limit | number | – | Max conversations (default 20) |
No output schema declared.
No examples provided.
recall_search Search recall ~121
Search everything the caller has said to an agent and been told, wherever they said it — the browser, email, or the command line. Use it when something was mentioned and you need to find where; notes_get is for a fact somebody wrote down on purpose
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Narrow to where it was said: web, mail, cli. Omit for everywhere |
| limit | number | – | Max results (default 20, max 200) |
| query | string | yes | What to look for — a word or phrase that was said |
No output schema declared.
No examples provided.
routes_directions Directions routes ~221
The turn-by-turn route between two places, with the distance for each instruction. Use ETA instead when only the travel time is wanted — this asks the provider for more and costs more
| Name | Type | Req | Description |
|---|---|---|---|
| arrive_by | string | – | Be there by this time, as RFC3339. Cannot be combined with depart_at |
| depart_at | string | – | When the journey starts, as RFC3339. Defaults to now |
| from | string | – | Where the journey starts, e.g. 'King's Cross, London' (or give from_lat/from_lon) |
| from_lat | number | – | Optional start latitude, if already known |
| from_lon | number | – | Optional start longitude, if already known |
| mode | string | – | How to travel: drive (default), walk, cycle or transit |
| to | string | – | Where the journey ends, e.g. 'Heathrow Airport' |
| to_lat | number | – | Optional end latitude, if already known |
| to_lon | number | – | Optional end longitude, if already known |
No output schema declared.
No examples provided.
routes_eta Travel time ~257
How long it takes to travel between two places, by road rather than as the crow flies. Can be asked about a future departure, or told when you need to arrive and answer when to leave
| Name | Type | Req | Description |
|---|---|---|---|
| arrive_by | string | – | Be there by this time, as RFC3339. Answers when to leave. Cannot be combined with depart_at |
| depart_at | string | – | When the journey starts, as RFC3339 (e.g. 2026-08-13T08:00:00Z). Defaults to now. Traffic and timetables are read for this time |
| from | string | – | Where the journey starts, e.g. 'King's Cross, London' (or give from_lat/from_lon) |
| from_lat | number | – | Optional start latitude, if already known |
| from_lon | number | – | Optional start longitude, if already known |
| mode | string | – | How to travel: drive (default), walk, cycle or transit |
| to | string | – | Where the journey ends, e.g. 'Heathrow Airport' |
| to_lat | number | – | Optional end latitude, if already known |
| to_lon | number | – | Optional end longitude, if already known |
No output schema declared.
No examples provided.
routes_nearest Nearest routes ~162
Given a starting point and several destinations, say which is quickest to reach and put them in order. Each destination is a separate routing lookup, so ask about the places you are actually choosing between rather than a long list
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Where you are starting from, e.g. 'Shoreditch, London' (or give from_lat/from_lon) |
| from_lat | number | – | Optional start latitude, if already known |
| from_lon | number | – | Optional start longitude, if already known |
| mode | string | – | How to travel: drive (default), walk, cycle or transit |
| to | array | yes | The places to compare, e.g. ['Heathrow', 'Gatwick', 'Stansted'] |
No output schema declared.
No examples provided.
shell_run Run shell ~168
Run a shell command in your account's container sandbox and get back what it wrote. A real shell in a container: pipes, redirection and && all work, the working directory is /work and files there persist between calls. Use it to build, test, run scripts and move files about. A non-zero exit code comes back in the response rather than as an error, so read the output — a failing build is an answer
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | A shell command to run, e.g. 'go test ./... 2>&1 | tail -40' |
| dir | string | – | Directory to run it in, under /work. Defaults to /work |
| timeout | number | – | Seconds to allow, up to the instance's maximum. Defaults to 120 |
No output schema declared.
No examples provided.
shell_write Write shell ~152
Put a file in your account's container sandbox, creating any missing directories. The only file operation that is not a shell command, because it is the one a shell is bad at: source is full of quotes and backticks and a heredoc will mangle it. The content arrives as a string and reaches the file without a shell seeing it. To read, list, search or change a file, use the shell — cat, ls, grep and sed are right there
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The whole file. This replaces what was there |
| path | string | yes | Where to put it, relative to /work — not to the directory your last command left you in. Missing directories are created |
No output schema declared.
No examples provided.
sms_history History sms ~57
Read the texts this account has sent and received, newest first. Both directions, which is why it is not called an inbox
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many messages to return, newest first (default 50, max 200) |
No output schema declared.
No examples provided.
sms_number Number sms ~30
The number texts are sent from, which numbers are verified as yours, and how many messages are left today
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sms_send Send sms ~181
Message somebody from this instance's number, by text or on WhatsApp. A text is charged per 160-character segment; WhatsApp is charged per 24-hour conversation and only reaches somebody who wrote in within the last day. Capped per day either way, and the recipient can stop it with STOP
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | How to send it: 'sms' (the default) or 'whatsapp'. WhatsApp only works with somebody who messaged this instance in the last 24 hours — reply on the channel they used |
| text | string | yes | What to say. A text is charged per 160-character segment, so brevity is not only good manners |
| to | string | yes | The number to message, in international format, e.g. +447700900123. Use contacts_find to turn a name into one |
No output schema declared.
No examples provided.
sms_source Source sms ~30
Read one stored message owned by the caller, by id
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stored message id |
No output schema declared.
No examples provided.
sms_sources Sources sms ~31
List stored message ids owned by the caller
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
sms_verify Verify sms ~81
Claim a number as your own, so texts arriving from it reach this account. Call it with just the number to have a code texted there, then again with the code
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | The code that was texted to that number. Omit to have one sent |
| number | string | yes | Your own number, in international format |
No output schema declared.
No examples provided.
social_list Browse social ~33
Read the latest social posts from the network
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional max number of posts (default all recent) |
No output schema declared.
No examples provided.
social_search Search social ~65
Search public posts on this instance by keyword. This is the instance's own feed, not the wider internet — use web_search for that
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
| query | string | yes | What to look for in posts on this instance |
No output schema declared.
No examples provided.
stream_list Browse stream ~35
Read what has happened here recently
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many entries to return (default 20, max 100) |
No output schema declared.
No examples provided.
tasks_create Create tasks ~109
Add a task. Assign it to the agent and it can pick the task up itself
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | me (default) or agent — assign to the agent and it can pick the task up |
| detail | string | – | Anything the doer needs to know: context, links, constraints |
| due | string | – | Optional deadline, RFC3339 or 2006-01-02 15:04 |
| title | string | yes | What is to be done |
No output schema declared.
No examples provided.
tasks_delete Delete tasks ~23
Remove a task
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's id |
No output schema declared.
No examples provided.
tasks_list Browse tasks ~69
List the caller's tasks, open ones first; optionally filtered by state
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum tasks, default 20, max 100 |
| offset | number | – | Tasks to skip |
| status | string | – | Optional filter: todo, doing, done, failed or blocked |
No output schema declared.
No examples provided.
tasks_next Next tasks ~22
The next task assigned to the agent — what to work on now
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tasks_read Read tasks ~27
Read one task owned by the caller
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's id |
No output schema declared.
No examples provided.
tasks_update Update tasks ~88
Change a task: its state, or the result of doing it
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | New detail |
| id | string | yes | The task's id |
| result | string | – | What came of it — the answer, the outcome, what was found |
| status | string | – | todo, doing, done, failed or blocked |
| title | string | – | New title |
No output schema declared.
No examples provided.
text_classify Classify text ~65
Sort text into one of the labels you give, with a confidence. For routing, triage and moderation. Capped at 30,000 characters
| Name | Type | Req | Description |
|---|---|---|---|
| labels | string | yes | Comma-separated labels to choose between |
| text | string | yes | The text to sort |
No output schema declared.
No examples provided.
text_extract Extract text ~75
Turn text into JSON matching a schema you give. Pass the fields you want as a JSON schema or a plain description; returns JSON only. Capped at 30,000 characters
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | yes | A JSON schema, or a plain description of the fields wanted |
| text | string | yes | The text to read |
No output schema declared.
No examples provided.
text_summarise Summarise text ~88
Summarise text into a few sentences. Pass style=bullets for a list, or a sentence count. Capped at 30,000 characters
| Name | Type | Req | Description |
|---|---|---|---|
| lines | number | – | Optional: roughly how many sentences or bullets |
| style | string | – | Optional: 'bullets' for a list, otherwise prose |
| text | string | yes | The text to summarise |
No output schema declared.
No examples provided.
text_translate Translate text ~56
Translate text into another language, preserving formatting. Capped at 30,000 characters
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to translate |
| to | string | yes | Target language, e.g. 'French' or 'ar' |
No output schema declared.
No examples provided.
transit_arrivals Arrivals transit ~87
What is due at a stop and when. Takes a stop name or an id. In London this is live from TfL — buses, tube, DLR, Overground and Elizabeth line. Elsewhere it is the published timetable, and says so
| Name | Type | Req | Description |
|---|---|---|---|
| stop | string | yes | Stop name or id, e.g. 'Oxford Circus' or 940GZZLUOXC |
No output schema declared.
No examples provided.
transit_buses Buses transit ~126
Where the buses actually are near a point right now — line, where each is heading and how far away, nearest first. England, from the Bus Open Data Service. This is position rather than prediction: it says what is moving, not when it reaches you
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitude of the point to look around |
| limit | number | – | How many to list, default 10 |
| lon | number | – | Longitude of the point |
| within_km | number | – | How far to look, in kilometres — default 2, most 25 |
No output schema declared.
No examples provided.
How do I install the mu.micro/mu MCP server?
mu.micro/mu is a hosted endpoint at https://micro.mu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · micro.mu
claude mcp add --transport http mu-micro-mu 'https://micro.mu/mcp'
What is the mu.micro/mu MCP server?
mu.micro/mu is an MCP server listed in the public MCP registry as mu.micro/mu. News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint. This page covers its hosted endpoint (https://micro.mu/mcp).
Is the mu.micro/mu MCP server safe to use?
mu.micro/mu scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mu.micro/mu MCP server expose?
mu.micro/mu exposes 170 tools: alerts_list, alerts_raise, alerts_update, apps_build, apps_builds, and 165 more. Their descriptions and schemas cost roughly 12,582 tokens of context every time the server is loaded.
Does the mu.micro/mu MCP server require authentication?
No. We connected to mu.micro/mu without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the mu.micro/mu MCP server still maintained?
mu.micro/mu is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.