field-notes

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.bitbucket.markedet/field-notes and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 6 Nov 2026. Not supplied by the maker.

• find_cards

  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 an

• get_card

  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'"}. Argume

• report_outcome

  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_wor

• ask_markedet

  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. F

• get_answer

  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":"...",