Add tool annotations to server-fetch (1 tool, 0 annotated)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Locate the single fetch tool registration in the @modelcontextprotocol/server-fetch package and review how its metadata is currently defined. Add the suggested readOnlyHint, destructiveHint, idempotentHint, and openWorldHint values; done means the fetch tool exposes those annotations without changing its HTTP GET behavior.
Written by the indexing model from the issue text.
Description
Request: Add tool annotations — @modelcontextprotocol/server-fetch
Context
The fetch server currently provides zero annotations on its 1 tool. For reference, @modelcontextprotocol/server-filesystem annotates all 14 of its tools with readOnlyHint, destructiveHint, and idempotentHint. We're requesting the same treatment here.
Current state — 0/1 tools annotated
| # | Tool | readOnlyHint |
destructiveHint |
idempotentHint |
openWorldHint |
|---|---|---|---|---|---|
| 1 | fetch |
— | — | — | — |
Suggested annotations
| # | Tool | readOnlyHint |
destructiveHint |
idempotentHint |
openWorldHint |
|---|---|---|---|---|---|
| 1 | fetch |
true |
false |
true |
true |
Rationale
fetch → readOnlyHint: true, idempotentHint: true, openWorldHint: true
This tool fetches a URL via HTTP GET and returns the content as markdown. It does not modify any data on the target server or locally. It is idempotent — fetching the same URL twice returns the same result (modulo server-side changes). It is open-world because it makes outbound HTTP requests to arbitrary URLs on the internet.
openWorldHint: true is particularly important here. The fetch tool can reach any URL, making it a key vector in multi-server setups where an agent could chain a read from a local tool (e.g. read_graph from the memory server) into an outbound fetch to exfiltrate data. Accurate annotations help clients enforce "allow reads, gate sends" policies.
Impact
This is a ~5 line metadata addition to the single tool registration. No behavior changes. The server-filesystem already sets the precedent for annotation coverage across reference servers.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/servers
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#4830 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/servers#4829 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
modelcontextprotocol/servers#4812 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
modelcontextprotocol/servers#4804 · 1 comment ·
-
README gate confirmation command can be used by any commenter, bypassing the "readme: pending" gate Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
modelcontextprotocol/servers#4796 ·
All issues in modelcontextprotocol/servers
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100