Is com.astranl/mcp up? Live MCP status
Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.
A stock client connected with no credential and negotiated 2026-07-28. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2026-07-28 |
| Server says it is | astranl-mcp 1.37.0 |
| Answered in | 281 ms |
| Endpoint checked | https://astranl.com/mcp/streamable |
| 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 | Published, does not validate: securitySchemes.none has the 0.3 shape (`type`), not a 1.0 scheme (and 1 more). A2A 1.0 shape; 6 skills; JSONRPC; 1 JWS signature (EdDSA; not verified)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://astranl.com/mcp/streamable/server-card (the one endpoint per origin the census asks, not this listing’s) |
| MCP server card (SEP-1649 location) | Published, does not validate: `protocolVersion` is required (and 1 more). SEP-1649 shape; streamable_http./.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://astranl.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 19 tools: ask_astranl, check_counterparty_nl, check_task, construction_economy, construction_events, construction_laws, construction_leadtimes, construction_natura, construction_permits, construction_summary, construction_tenders, construction_zones, create_task, fetch, get_evidence, ground_astranl, record_counterparty_check, search, verify_astranl.
Its tools changed between 2026-09 and 2026-10:
- Added (13):
check_counterparty_nl,construction_economy,construction_events,construction_laws,construction_leadtimes,construction_natura,construction_permits,construction_summary,construction_tenders,construction_zones,ground_astranl,record_counterparty_check,verify_astranl ask_astranl: description, input schema changedcheck_task: description, input schema changedcreate_task: description, input schema changedget_evidence: 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 | com.astranl/mcp |
|---|---|
| Title | AstraNL |
| Description | Dutch construction facts with measured accuracy + NL coordination. Never holds third-party funds. |
| Endpoint | https://astranl.com/mcp/streamable |
| Other endpoints | https://astranl.com/mcp/sse |
| Publisher repository | none listed |
| Version | 1.37.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