Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ar.com.sofiaferro/portfolio

REMOTE · WWW.SOFIAFERRO.COM.AR · SCANNED SEP 27

Sofia Ferro's portfolio: projects, blog posts, JSON Resume and a contact tool (es/en).

+3 this week 71 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 719 tokens (~143/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "contact" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ar.com.sofiaferro/portfolio MCP server?

ar.com.sofiaferro/portfolio is a hosted endpoint at https://www.sofiaferro.com.ar/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.sofiaferro.com.ar

# add to Claude Code
claude mcp add --transport http ar-com-sofiaferro-portfolio 'https://www.sofiaferro.com.ar/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ar-com-sofiaferro-portfolio": {
      "url": "https://www.sofiaferro.com.ar/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ar-com-sofiaferro-portfolio": {
      "type": "http",
      "url": "https://www.sofiaferro.com.ar/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ar-com-sofiaferro-portfolio]
url = "https://www.sofiaferro.com.ar/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ar-com-sofiaferro-portfolio": {
      "type": "remote",
      "url": "https://www.sofiaferro.com.ar/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ar-com-sofiaferro-portfolio --url 'https://www.sofiaferro.com.ar/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ar-com-sofiaferro-portfolio:
    url: "https://www.sofiaferro.com.ar/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ar-com-sofiaferro-portfolio": {
      "Transport": "http",
      "Url": "https://www.sofiaferro.com.ar/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ar-com-sofiaferro-portfolio -t streamable-http -u 'https://www.sofiaferro.com.ar/api/mcp'
// mcp.json
{
  "mcpServers": {
    "ar-com-sofiaferro-portfolio": {
      "type": "http",
      "url": "https://www.sofiaferro.com.ar/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Sept 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 27 Sept 2026 · Probed https://www.sofiaferro.com.ar/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.sofiaferro.com.ar CN=YR1,O=Let's Encrypt,C=US 18 Aug 2026 16 Nov 2026 RSA 2048 SHA256-RSA 5c1b585f62596c8f8c8a1dc920dcb1ac662
SANs: www.sofiaferro.com.ar
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.sofiaferro.com.ar. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ar. present 19606 8 Verified
com.ar. present 1474 8 Verified
sofiaferro.com.ar. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.sofiaferro.com.ar/api/mcp Verified 200
http (plaintext) http://www.sofiaferro.com.ar/api/mcp HTTPS enforced 308 https://www.sofiaferro.com.ar/api/mcp
MCP tools · 5 exposed · ~555 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
contact ~155

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.

NameTypeReqDescription
contact_infostringyesHow Sofia can reply: an email address or similar.
messagestringyesThe message for Sofia (max 2000 characters).
namestringyesName of the person (or agent + principal) reaching out.
purposestring–Why you are reaching out: "intro_call", "collab" or "other".

No output schema declared.

No examples provided.

get_manifesto ~84

Sofia Ferro's manifesto on programming as embodied practice — error as path, faith in the infinite loop of trying once more. Returns title, summary and the full markdown text. For her ongoing thinking, see X: https://x.com/svfonx

NameTypeReqDescription
localestring–Content language: "es" (Spanish, default) or "en" (English).

No output schema declared.

No examples provided.

get_project ~97

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.

NameTypeReqDescription
localestring–Content language: "es" (Spanish, default) or "en" (English).
slugstringyesProject slug, e.g. "pit0nisa" (see list_projects).

No output schema declared.

No examples provided.

get_resume ~90

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

NameTypeReqDescription
localestring–Content language: "es" (Spanish, default) or "en" (English).

No output schema declared.

No examples provided.

list_projects ~129

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.

NameTypeReqDescription
categorystring–Filter by category. One of: literatura-expandida, bots, iot, hardware, creative-coding, instalacion.
localestring–Content language: "es" (Spanish, default) or "en" (English).

No output schema declared.

No examples provided.

Common questions

What is the ar.com.sofiaferro/portfolio MCP server?

ar.com.sofiaferro/portfolio is an MCP server listed in the public MCP registry as ar.com.sofiaferro/portfolio. Sofia Ferro's portfolio: projects, blog posts, JSON Resume and a contact tool (es/en). This page covers its hosted endpoint (https://www.sofiaferro.com.ar/api/mcp).

Is the ar.com.sofiaferro/portfolio MCP server safe to use?

ar.com.sofiaferro/portfolio scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ar.com.sofiaferro/portfolio MCP server expose?

ar.com.sofiaferro/portfolio exposes 5 tools: get_resume, list_projects, get_project, get_manifesto, contact. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.

Does the ar.com.sofiaferro/portfolio MCP server require authentication?

No. We connected to ar.com.sofiaferro/portfolio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ar.com.sofiaferro/portfolio MCP server still maintained?

ar.com.sofiaferro/portfolio is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.