Skip to content

field-notes MCP server

io.bitbucket.markedet/field-notesmarkedet.bitbucket.iostreamable-httpv0.5.2Scanned

Paste an exact error string, get a checked fix and a verify step from the Agent Field Guide. As is.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 3
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the field-notes MCP server can do

The field-notes MCP server is published by markedet.bitbucket.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: report_outcome and ask_markedet), but cannot delete data. 3 tools only read.

3 tools read private data (find_cards, get_card and get_answer); 3 tools bring in text other people can write (find_cards, ask_markedet and get_answer).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • ask_markedetReturns a ticket for a custom answer to your question; fetch the answer with get_answer.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "ticket": it reads issues, which other people can write.

    Findings

    • Warn

      The server marks "ask_markedet" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "return": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • report_outcomeRecords whether a fix from find_cards or an answer from ask_markedet worked.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Records whether a fix from find_cards or an answer from ask_markedet worked. Returns {"recorded":true,"follow_up":false}. Arguments: ticket from find_cards or ask_markedet; outcome worked, did_not_work or partly; satisfied yes, no or unsure; optional card_id; 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. There is no free-text field. Good for 'the verify step passed'.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
Only reads 3Show 3 read-only tools
  • find_cardsReturns 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,…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "find_cards" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "return" and "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_answerReturns the status of an ask_markedet ticket: queued (with position), answering, answered (with the answer and the field notes it names) or failed.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_answer" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "return" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_cardReturns one field note in full by id (PC-..., DP-..., NH-...).Reads private dataNo findings

    Why it is in this group

    • The name "get_card" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    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). Good for reading the snippet, cause and source excerpt of a card that find_cards returned.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://unstuckagents.com/notes/mcp: tools/list returned 5 tools to an anonymous client, including report_outcome (write), ask_markedet (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "ask_markedet" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "return": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
    • Changed:get_cardOnly readsdescriptioninputSchema

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http field-notes https://unstuckagents.com/notes/mcp
claude mcp add --transport http field-notes https://unstuckagents.com/notes/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__field-notes__find_cards",
      "mcp__field-notes__get_card",
      "mcp__field-notes__get_answer"
    ],
    "ask": [
      "mcp__field-notes__report_outcome",
      "mcp__field-notes__ask_markedet"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as field-notes. Review it before you use it.

Capability tags behind 4 rules
  • mcp__field-notes__find_cards private-data, untrusted-input
  • mcp__field-notes__get_card private-data
  • mcp__field-notes__ask_markedet untrusted-input
  • mcp__field-notes__get_answer private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.bitbucket.markedet/field-notes/verify?hash=9fb6a78ce6704bdf6e3252d3f8a510de653f07653d3ff4fa491982ed1e5a4b0a" | jq -e '.changed == false'

Pinned hash 9fb6a78ce670, from Nov 11, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.bitbucket.markedet/field-notes/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.bitbucket.markedet/field-notes
[![Anlyon Radar](https://radar.anlyon.com/badge/io.bitbucket.markedet/field-notes.svg)](https://radar.anlyon.com/servers/io.bitbucket.markedet/field-notes)

Source: MCP Registry. Synced Nov 11, 2026, 08:17 UTC.

field-notes MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the field-notes MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the field-notes MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the field-notes MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the field-notes MCP server have?

5 tools: 2 write, 3 read. report_outcome, ask_markedet, find_cards, get_card and get_answer.

Does the field-notes MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the field-notes MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the field-notes MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.