portfolio MCP server
ar.com.sofiaferro/portfoliosofiaferro.com.arstreamable-httpv1.0.0Scanned
Sofia Ferro's portfolio: projects, blog posts, JSON Resume and a contact tool (es/en).
5 tools: 1 do something that can't be undone and 4 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 1
- 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 portfolio MCP server can do
The portfolio MCP server is published by sofiaferro.com.ar, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (contact), but cannot delete data. 4 tools only read.
1 tool reads private data (get_resume); 1 tool can send data out of your system (contact).
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 12, 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.
5 tools
Can't be undone 1Claude Code: ask
contactSend a message to Sofia Ferro (delivered to her inbox by email).Can send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Send a message to Sofia Ferro (delivered to her inbox by email). Use this to propose an intro call, a collaboration, or anything else on behalf of your user. Always include who is reaching out and how Sofia can reply (email or other contact info). Rate-limited; if unavailable, email svf.inbox@gmail.com directly instead.
Only reads 4Show 4 read-only tools
get_manifestoSofia Ferro's manifesto on programming as embodied practice — error as path, the practice that stays when everything else changes.No findings
Why it is in this group
- The name "get_manifesto" says "get": a word for reading.
Description, as the server wrote it Sofia Ferro's manifesto on programming as embodied practice — error as path, the practice that stays when everything else changes. Returns title, summary and the full markdown text. For her ongoing thinking, see X: https://x.com/svfonx
get_projectGet one of Sofia Ferro's projects in full: metadata (category, date, tech, links, images) plus title, summary and the complete markdown body.No findings
Why it is in this group
- The name "get_project" says "get": a word for reading.
Description, as the server wrote it Get one of Sofia Ferro's projects in full: metadata (category, date, tech, links, images) plus title, summary and the complete markdown body. Use list_projects first to discover valid slugs.
get_resumeSofia Ferro's full resume as a JSON Resume v1.0.0 document (basics, skills, projects).Reads private dataNo findings
Why it is in this group
- The name "get_resume" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it Sofia Ferro's full resume as a JSON Resume v1.0.0 document (basics, skills, projects). The resume is maintained in English only, so the locale parameter is currently ignored. Canonical URL: https://www.sofiaferro.com.ar/api/resume.json
list_projectsList Sofia Ferro's published projects (electronic art, expanded literature, bots, IoT, hardware, creative coding, installations).No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it List Sofia Ferro's published projects (electronic art, expanded literature, bots, IoT, hardware, creative coding, installations). Returns slug, title, summary, category, date, tech stack and links for each project, newest first. Optionally filter by category. Use get_project with a slug for the full write-up.
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 untrusted-input.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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 20, 2026, 18:30 UTC, unchanged since Oct 22, 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://www.sofiaferro.com.ar/api/mcp: tools/list returned 5 tools to an anonymous client, including contact (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:get_manifestoOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http portfolio https://www.sofiaferro.com.ar/api/mcpclaude mcp add --transport http portfolio https://www.sofiaferro.com.ar/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__portfolio__get_resume",
"mcp__portfolio__list_projects",
"mcp__portfolio__get_project",
"mcp__portfolio__get_manifesto"
],
"ask": [
"mcp__portfolio__contact"
],
"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 portfolio. Review it before you use it.
Capability tags behind 2 rules
- mcp__portfolio__get_resume private-data
- mcp__portfolio__contact outbound
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/ar.com.sofiaferro/portfolio/verify?hash=b0564a381a8dd799700f91b1fcc64412ab787bcbb1e41860bf3f0ab47b2df741" | jq -e '.changed == false'Pinned hash b0564a381a8d, from Nov 12, 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/ar.com.sofiaferro/portfolio/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ar.com.sofiaferro/portfolio)Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.
portfolio MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the portfolio MCP server safe?
- No scan can promise that. What its definitions show: 5 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 portfolio MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the portfolio MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: contact.
What tools does the portfolio MCP server have?
- 5 tools: 1 irreversible, 4 read. contact, get_resume, list_projects, get_project and get_manifesto.
Does the portfolio MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the portfolio MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): contact.
Has the portfolio MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.