ShareNotes MCP server
dev.sharenotes/notessharenotes.devstreamable-httpv1.0.0Scanned
Create and read text notes at memorable links like sharenotes.dev/blue-fox-42. No key, no account.
2 tools: 1 do something that can't be undone and 1 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 ShareNotes MCP server can do
The ShareNotes MCP server is published by sharenotes.dev, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_note), but cannot delete data. 1 tool only reads.
1 tool reads private data (read_note); 2 tools bring in text other people can write (create_note and read_note).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.0.
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.
2 tools
Can't be undone 1Claude Code: ask
create_notePublish text as a note on sharenotes.dev and get back a short, human-readable link (like https://sharenotes.dev/blue-fox-42) to give to a person.Reads text others writeNo findings
Why it is in this group
- The name "create_note" says "create": a word for a change.
- The description's first verb is "publish": a word for a change that another call does not undo.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Publish text as a note on sharenotes.dev and get back a short, human-readable link (like https://sharenotes.dev/blue-fox-42) to give to a person. Use it when the user wants to share text, code, logs or instructions with someone else, or move text to another device. Anyone with the link can read the note, and notes are stored on the server, not end-to-end encrypted — never use it for passwords, API keys or other secrets. The note expires after 7 days unless you set expiresIn. Set burnAfterRead for a note that is destroyed the first time a person opens it. Returns the link and the expiry time.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
read_noteRead the text of a note on sharenotes.dev, given its link (https://sharenotes.dev/blue-fox-42) or just its name (blue-fox-42).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "read_note" says "read": a word for reading.
What it can reach
- private-dataThe name "read_note" says "read" and "note": it reads notes.
- private-dataThe description's first sentence says "read" and "note": it reads notes.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it Read the text of a note on sharenotes.dev, given its link (https://sharenotes.dev/blue-fox-42) or just its name (blue-fox-42). Use it when the user gives you a ShareNotes link and asks about its contents. Returns plain text: notes written in the ShareNotes web editor are converted from HTML. It does not open PIN-protected notes, and it does not open delete-after-reading notes, because opening one destroys it — for those, ask the user to open the link in a browser.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: 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 data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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.
Looked at Nov 16, 2026, 14:22 UTC, unchanged since Oct 25, 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
- 1
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://sharenotes.dev/api/mcp: tools/list returned 2 tools to an anonymous client, including create_note (irreversible)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:read_noteOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http notes https://sharenotes.dev/api/mcpclaude mcp add --transport http notes https://sharenotes.dev/api/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__notes__read_note"
],
"ask": [
"mcp__notes__create_note"
],
"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 notes. Review it before you use it.
Capability tags behind 2 rules
- mcp__notes__create_note untrusted-input
- mcp__notes__read_note 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/dev.sharenotes/notes/verify?hash=ec08ff80dca20f6e7617f9eefb953888e37c43ffe269cd92c42c1f25583199bb" | jq -e '.changed == false'Pinned hash ec08ff80dca2, from Nov 9, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.sharenotes/notes/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.sharenotes/notes)Source: MCP Registry. Synced Oct 25, 2026, 08:17 UTC.
ShareNotes MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ShareNotes MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ShareNotes MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ShareNotes MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_note.
What tools does the ShareNotes MCP server have?
- 2 tools: 1 irreversible, 1 read. create_note and read_note.
Does the ShareNotes MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ShareNotes MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ShareNotes MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.