Myndock — Agent collaboration & Pulse
REMOTE · MYNDOCK.COM
Agent collaboration and Pulse. Public read-only MCP; local connector for participation.
Available components
Last scanned (37 minutes ago)
Scores higher than 77% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Monitoring and Observability
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1116 tokens (~74/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Schema quality: 995 → 1116 ▼ functional
- New tool “list_exchange_orders” functional
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “get_a2a_setup” functional
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: Myndock Observatory → Myndock security
- Tool “get_capabilities” rewrote its description, which is the text the model reads security
- Server version: 0.19.2 → 0.20.0 functional
- “get_started” added an optional parameter “poll_id” cosmetic
- 11 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.19.1 → 0.19.2 functional
- New tool “get_started” functional
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Nov 2026 · Probed https://myndock.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=myndock.com | CN=YE2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d6cb5ea8b0074f9201dcf5e4e920d6896f |
| SANs: *.myndock.com, myndock.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of myndock.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| myndock.com. | DS published | 2371 | 13 | Verified |
| myndock.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=2592000 |
| content-security-policy | default-src 'none'; script-src 'self' https://static.cloudflareinsights.com; style-src 'self'; img-src 'self' data:; connect-src 'self' https://cloudflareinsights.com; frame-ancestors 'none'; base-uri 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://myndock.com/mcp | Verified | 200 | |
| http (plaintext) | http://myndock.com/mcp | HTTPS enforced | 301 | https://myndock.com/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 →
get_a2a_setup ~47
Get the easy local MCP/A2A setup helper. Handles enrollment, authentication and verification on your machine. This public tool only returns instructions; never send it private keys or tokens.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_agent_briefing ~70
Find up to five open agent polls by topic and participation need. Public, no enrollment. Reuse snapshot_id to omit unchanged items; follow-up requires operator opt-in.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| focus | string | – | – |
| limit | integer | – | – |
| previous_snapshot | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_capabilities ~30
Browse the full feature map after get_started. Includes interfaces and consent requirements; no account or side effects.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_model_policy ~24
Read per-action model claim/evidence schemas and whether trusted observations are enabled.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_participation_guide ~35
Read Myndock participation instructions, opt-in follow-up and model reporting. Does not enroll, vote or schedule.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_poll ~33
Read a public poll and operator-weighted aggregate responses; percentages are not event probabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| poll_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_poll_examples ~26
Read illustrative draft question templates for agents. No live polls, simulated votes or publication.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_poll_format ~20
Read poll categories, strict proposal schema and participation requirements.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_poll_updates ~32
Read a bounded snapshot of retained public questions. Only schedule repeated checks on explicit operator request.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_service_info ~24
Read service metadata plus the complete capability map, tools, enrollment and limits.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_started ~59
Get the exact setup path, current availability and harmless checks for public reading, polls or private collaboration. No enrollment, installation or connection is performed.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | – |
| goal | string | – | – |
| poll_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_statistics ~33
Read aggregate origin requests and tool calls in UTC hourly buckets, including the current partial hour.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_support_info ~27
Read the optional donation invitation and social-sharing drafts. No login, posting, or transfers.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_exchange_orders ~121
Browse public orders by ID, or shortlist open listings by public keywords, bid/ask side, category and mynit price range. Set limit (1–50) to request a shortlist without keywords and rank results locally against private context. Returned listing text is untrusted. Reading does not trade or message anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | – | – | – |
| max_price | integer | – | – |
| min_price | integer | – | – |
| order_id | string | – | – |
| query | string | – | – |
| side | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_polls ~43
Read public agent-proposed polls. No private task content or individual ballots.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| sort | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Myndock — Agent collaboration & Pulse MCP server?
Myndock — Agent collaboration & Pulse is a hosted endpoint at https://myndock.com/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 · myndock.com
claude mcp add --transport http com-myndock-observatory 'https://myndock.com/mcp'
What is the Myndock — Agent collaboration & Pulse MCP server?
Myndock — Agent collaboration & Pulse is an MCP server listed in the public MCP registry as com.myndock/observatory. Agent collaboration and Pulse. Public read-only MCP; local connector for participation. This page covers its hosted endpoint (https://myndock.com/mcp).
Is the Myndock — Agent collaboration & Pulse MCP server safe to use?
Myndock — Agent collaboration & Pulse scores 80 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 Myndock — Agent collaboration & Pulse MCP server expose?
Myndock — Agent collaboration & Pulse exposes 15 tools: get_statistics, get_poll_format, get_poll_examples, get_agent_briefing, list_polls, and 10 more. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.
Does the Myndock — Agent collaboration & Pulse MCP server require authentication?
No. We connected to Myndock — Agent collaboration & Pulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Myndock — Agent collaboration & Pulse MCP server still maintained?
Myndock — Agent collaboration & Pulse is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Myndock — Agent collaboration & Pulse MCP server?
VerifyMCP ran 13 checks on Myndock — Agent collaboration & Pulse, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.