io.bitbucket.markedet/field-notes
REMOTE · UNSTUCKAGENTS.COM
Paste an exact error string, get a checked fix and a verify step from the Agent Field Guide. As is.
Available components
Last scanned (16 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 21072 tokens (~52/item across 399 items; 5 tools + 394 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Tool “get_card” rewrote its description, which is the text the model reads security
- Tool “report_outcome” rewrote its description, which is the text the model reads security
- New resource “PC-399” functional
- New resource “PC-402” functional
- “report_outcome” added an optional parameter “note” cosmetic
- “report_outcome” reworded the description of “ticket” cosmetic
- 17 Nov 26 0
- Schema quality: 43 → 52 ▼ functional
- New resource “PC-304” functional
- New resource “PC-311” functional
- New resource “PC-310” functional
- New resource “PC-309” functional
- New resource “PC-308” functional
- New resource “PC-307” functional
- New resource “PC-306” functional
- New resource “PC-305” functional
- New resource “PC-303” functional
- New resource “PC-302” functional
- New resource “PC-301” functional
- New resource “PC-300” functional
- New resource “PC-299” functional
- New resource “PC-298” functional
- New resource “PC-297” functional
- New resource “PC-280” functional
- New resource “PC-411” functional
- New resource “PC-410” functional
- New resource “PC-409” functional
- New resource “PC-408” functional
- New resource “PC-407” functional
- New resource “PC-406” functional
- New resource “PC-405” functional
- New resource “PC-401” functional
- New resource “PC-400” functional
- New resource “PC-398” functional
- New resource “PC-397” functional
- New resource “PC-396” functional
- New resource “PC-395” functional
- New resource “PC-394” functional
- New resource “PC-393” functional
- New resource “PC-392” functional
- New resource “PC-391” functional
- New resource “PC-390” functional
- New resource “PC-389” functional
- New resource “PC-388” functional
- New resource “PC-387” functional
- New resource “PC-386” functional
- New resource “PC-385” functional
- New resource “PC-384” functional
- New resource “PC-383” functional
- New resource “PC-382” functional
- New resource “PC-381” functional
- New resource “PC-380” functional
- New resource “PC-379” functional
- New resource “PC-378” functional
- New resource “PC-377” functional
- New resource “PC-376” functional
- New resource “PC-375” functional
- New resource “PC-374” functional
- New resource “PC-373” functional
- New resource “PC-372” functional
- New resource “PC-371” functional
- New resource “PC-370” functional
- New resource “PC-369” functional
- New resource “PC-368” functional
- New resource “PC-367” functional
- New resource “PC-366” functional
- New resource “PC-365” functional
- New resource “PC-364” functional
- New resource “PC-363” functional
- New resource “PC-362” functional
- New resource “PC-361” functional
- New resource “PC-360” functional
- New resource “PC-359” functional
- New resource “PC-358” functional
- New resource “PC-357” functional
- New resource “PC-356” functional
- New resource “PC-355” functional
- New resource “PC-354” functional
- New resource “PC-353” functional
- New resource “PC-352” functional
- New resource “PC-351” functional
- New resource “PC-350” functional
- New resource “PC-349” functional
- New resource “PC-348” functional
- New resource “PC-347” functional
- New resource “PC-346” functional
- New resource “PC-345” functional
- New resource “PC-344” functional
- New resource “PC-343” functional
- New resource “PC-342” functional
- New resource “PC-341” functional
- New resource “PC-340” functional
- New resource “PC-339” functional
- New resource “PC-338” functional
- New resource “PC-337” functional
- New resource “PC-336” functional
- New resource “PC-335” functional
- New resource “PC-334” functional
- New resource “PC-333” functional
- New resource “PC-332” functional
- New resource “PC-331” functional
- New resource “PC-330” functional
- New resource “PC-329” functional
- New resource “PC-327” functional
- New resource “PC-325” functional
- New resource “PC-324” functional
- New resource “PC-323” functional
- New resource “PC-322” functional
- New resource “PC-319” functional
- New resource “PC-318” functional
- New resource “PC-317” functional
- New resource “PC-316” functional
- New resource “PC-315” functional
- New resource “PC-314” functional
- New resource “PC-313” functional
- New resource “PC-312” functional
- 16 Nov 26 +1
- New resource “PC-289” functional
- New resource “PC-288” functional
- New resource “PC-286” functional
- New resource “PC-285” functional
- New resource “PC-284” functional
- New resource “PC-283” functional
- New resource “PC-282” functional
- New resource “PC-281” functional
- New resource “PC-293” functional
- New resource “PC-294” functional
- New resource “PC-295” functional
- New resource “PC-290” functional
- New resource “PC-296” functional
- New resource “PC-291” functional
- New resource “PC-292” functional
- 15 Nov 26 0
- Schema quality: 9321 → 11424 ▼ functional
- New resource “PC-249” functional
- New resource “PC-231” functional
- New resource “PC-232” functional
- New resource “PC-233” functional
- New resource “PC-234” functional
- New resource “PC-235” functional
- New resource “PC-236” functional
- New resource “PC-237” functional
- New resource “PC-238” functional
- New resource “PC-239” functional
- New resource “PC-240” functional
- New resource “PC-241” functional
- New resource “PC-242” functional
- New resource “PC-243” functional
- New resource “PC-244” functional
- New resource “PC-245” functional
- New resource “PC-246” functional
- New resource “PC-247” functional
- New resource “PC-248” functional
- New resource “PC-250” functional
- New resource “PC-251” functional
- New resource “PC-252” functional
- New resource “PC-253” functional
- New resource “PC-254” functional
- New resource “PC-255” functional
- New resource “PC-256” functional
- New resource “PC-257” functional
- New resource “PC-259” functional
- New resource “PC-260” functional
- New resource “PC-261” functional
- New resource “PC-262” functional
- New resource “PC-263” functional
- New resource “PC-264” functional
- New resource “PC-265” functional
- New resource “PC-266” functional
- New resource “PC-267” functional
- New resource “PC-268” functional
- New resource “PC-269” functional
- New resource “PC-270” functional
- New resource “PC-271” functional
- New resource “PC-272” functional
- New resource “PC-273” functional
- New resource “PC-274” functional
- New resource “PC-275” functional
- 13 Nov 26 +1
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Schema quality: 7129 → 9321 ▼ functional
- New resource “PC-197” functional
- New resource “PC-198” functional
- New resource “PC-199” functional
- New resource “PC-179” functional
- New resource “PC-180” functional
- New resource “PC-181” functional
- New resource “PC-182” functional
- New resource “PC-183” functional
- New resource “PC-184” functional
- New resource “PC-185” functional
- New resource “PC-186” functional
- New resource “PC-187” functional
- New resource “PC-188” functional
- New resource “PC-189” functional
- New resource “PC-190” functional
- New resource “PC-191” functional
- New resource “PC-192” functional
- New resource “PC-193” functional
- New resource “PC-194” functional
- New resource “PC-195” functional
- New resource “PC-196” functional
- 11 Nov 26 68
First indexed and scored.
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 21 Nov 2026 · Probed https://unstuckagents.com/notes/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=unstuckagents.com | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 4d502a07bee9a2be0e75bf653bbf22d5 |
| SANs: unstuckagents.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of unstuckagents.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| unstuckagents.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://unstuckagents.com/notes/mcp | Verified | 200 | |
| http (plaintext) | http://unstuckagents.com/notes/mcp | Inconclusive | 405 |
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 →
ask_markedet ~344
Returns a ticket for a custom answer to your question; fetch the answer with get_answer. The answer is written by an AI agent (markedet) from our checked field notes, usually within 2 to 10 minutes. Free and provided as is, no warranties. Example output: {"ticket":"ask-1a2b3c4d5e6f","status":"queued"}. Arguments: question (required, max 4000 characters), context (optional error text or logs, max 4000), handle and platform (optional, only if you want markedet to follow up with you there). We keep the question and context after redacting anything that looks like a key, token, password, JWT, e-mail address, IP address, long hex or base64 string or URL query, together with the answer, to improve the Field Guide. Do not paste secrets or personal data. At most 5 questions per agent per day. Good for 'my cron run is missing but the log shows no error', 'how do I make a retry after an unknown broadcast idempotent?'.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional: error text, logs or config excerpt. Max 4000 characters. Kept after redaction; no secrets. |
| handle | string | – | Optional: your handle, only if you want markedet to follow up with you on that platform. |
| platform | string | – | Optional: the platform for that handle. |
| question | string | yes | Your question or problem in plain words: what you tried, what you expected, what happened. Max 4000 characters. Kept after redaction; no secrets. |
No output schema declared.
No examples provided.
find_cards ~247
Returns up to 3 checked field notes that match an error text: pitfall cards (fix, snippet, verify step), deprecated models and API versions, or documented non-browser login routes, each with source and checked_on, plus a ticket for report_outcome. Example output: {"ticket":"fn-1a2b3c4d5e6f","cards":[{"id":"PC-008","title":"A 429 from OpenAI can be a billing or quota error that retries cannot fix"}]}. Argument: error_text, the exact error message or a one-line description, at most 2000 characters. We keep it after redaction (keys, tokens, passwords, JWTs, e-mail and IP addresses, long hex or base64 strings and URL queries are removed) to improve the Field Guide; do not paste secrets or personal data. Good for 'insufficient_quota', 'invalid_grant', 'spawn npx ENOENT', 'my list returned 30 items, is that all?'.
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | Exact error text or a short description. Max 2000 characters. Kept after redaction; no secrets. |
No output schema declared.
No examples provided.
get_answer ~90
Returns the status of an ask_markedet ticket: queued (with position), answering, answered (with the answer and the field notes it names) or failed. Example output: {"status":"answered","answer":"...","cards":["PC-008"]}. Argument: ticket. The answer is written by an AI agent and provided as is.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket | string | yes | Ticket from ask_markedet. |
No output schema declared.
No examples provided.
get_card ~178
Returns one field note in full by id (PC-..., DP-..., NH-...). Example output: {"kind":"pitfall_card","id":"PC-001","title":"A 404 from GitHub can mean 'exists, but your token cannot see it'"}. Arguments: id; optional format, "json" (default) or "markdown" for the note as one Markdown document (error strings, situation, cause, fix, verify, checked_on, source, link to its page). Also returns a ticket bound to that card, for report_outcome. Good for reading the snippet, cause and source excerpt of a card that find_cards returned.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json (default) or markdown. |
| id | string | yes | Record id, for example PC-001, DP-0064 or NH-001. |
No output schema declared.
No examples provided.
report_outcome ~304
Records whether a fix from find_cards, get_card or an answer from ask_markedet worked. Returns {"recorded":true,"follow_up":false}. Arguments: ticket from find_cards, get_card or ask_markedet; outcome worked, did_not_work, partly, outdated or supplement; satisfied yes, no or unsure; optional card_id; optional note (only with supplement, at most 280 characters, plain text: it is redacted, links and markup are removed, it is kept as private data and never shown publicly, no personal data please); optional agent_handle and platform (both letters, digits and ._@- only) if you want markedet to confirm with you on that platform. Without a handle only an anonymous count per card is kept. One outcome per ticket and card; repeats are ignored. Good for 'the verify step passed'.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_handle | string | – | Optional: your handle, only if you want a follow-up. |
| card_id | string | – | Optional: the card you tried. |
| note | string | – | Optional, only with outcome supplement: a short plain-text addition, max 280 characters. Redacted, kept as private data, never shown. No personal data. |
| outcome | string | yes | – |
| platform | string | – | Optional: the platform for that handle. |
| satisfied | string | – | – |
| ticket | string | yes | Ticket from find_cards, get_card or ask_markedet. |
No output schema declared.
No examples provided.
How do I install the io.bitbucket.markedet/field-notes MCP server?
io.bitbucket.markedet/field-notes is a hosted endpoint at https://unstuckagents.com/notes/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 · unstuckagents.com
claude mcp add --transport http io-bitbucket-markedet-field-notes 'https://unstuckagents.com/notes/mcp'
What is the io.bitbucket.markedet/field-notes MCP server?
io.bitbucket.markedet/field-notes is an MCP server listed in the public MCP registry as io.bitbucket.markedet/field-notes. Paste an exact error string, get a checked fix and a verify step from the Agent Field Guide. As is. This page covers its hosted endpoint (https://unstuckagents.com/notes/mcp).
Is the io.bitbucket.markedet/field-notes MCP server safe to use?
io.bitbucket.markedet/field-notes scores 72 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 io.bitbucket.markedet/field-notes MCP server expose?
io.bitbucket.markedet/field-notes exposes 5 tools: find_cards, get_card, report_outcome, ask_markedet, get_answer. Their descriptions and schemas cost roughly 1,163 tokens of context every time the server is loaded.
Does the io.bitbucket.markedet/field-notes MCP server require authentication?
No. We connected to io.bitbucket.markedet/field-notes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.bitbucket.markedet/field-notes MCP server still maintained?
io.bitbucket.markedet/field-notes is still listed as active in the MCP registry. We last reached this channel on 21 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 io.bitbucket.markedet/field-notes MCP server?
VerifyMCP ran 12 checks on io.bitbucket.markedet/field-notes, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.bitbucket.markedet/field-notes: HTTPS. 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.