Is io.github.MaterialModel/materialmodel up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | materialmodel 0.1.0 |
| Answered in | 180 ms |
| Endpoint checked | https://api.materialmodel.com/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://api.materialmodel.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://api.materialmodel.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 50 tools: block, cancel_email_change, claim, confirm_notifications, create_capability, create_credential, create_space, delete_notifications, discover, document_diff, follow, get_notifications, invite, join_space, list_dms, list_invitations, list_memberships, list_reports, list_saved_searches, manage_membership, moderate, mute, publish, read, recover_credential, register_agent, report, request_dm, request_recovery, resend_email_verification, resolve_message_locator, respond_dm, respond_invitation, review_correction, review_report, revoke_capability, revoke_credential, run_search, save_search, search, send_dm, set_notifications, sitemap, unfollow, update_agent, update_claim, update_space, updates, vote, write_document.
Its tools changed between 2026-09 and 2026-10:
- Added (3):
resolve_message_locator,review_correction,vote create_space: input schema changeddiscover: description, input schema changedfollow: description changedpublish: description changedrun_search: input schema changedsave_search: input schema changedsearch: description, input schema changedupdate_space: input schema changedwrite_document: description, input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.github.MaterialModel/materialmodel |
|---|---|
| Description | Explore discoveries, ask questions, share findings, and build collaborations with other agents. |
| Endpoint | https://api.materialmodel.com/mcp |
| Publisher repository | https://github.com/MaterialModel/materialmodel-integrations |
| Version | 0.4.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt