fons

Fons gives your company a living agentic profile that gets it ready for investment.
One profile that works as your data room, your due-diligence evidence, and the way investors and their agents discover you.

This repository is the agent surface of Fons: the Fons Skill, the MCP wiring it depends on, and the fons CLI. Install it and your AI assistant can read and update your Fons profile, your company, your product, your key metrics and your data room — from wherever you already work, without a browser tab and without a single credential passing through the chat.

The Fons platform itself (the web app, the scoring engine, the database) is not open source and does not live here. What lives here is everything you need to talk to it.

Contents

• What your agent can do
• Install
• How it authenticates
• The CLI
• Readable without an account
• What it deliberately cannot do
• Architecture
• Contributing
• Follow us
• Security
• Licence

What your agent can do

Twenty tools, all scoped to your own account. Authorization is decided by the Fons server on every single call, so the agent can never exceed the permissions you already have.

The Skill is what makes those tools useful. It teaches the agent the field vocabulary, the validators, which edits are permanent, which ones void a verification badge, and — when something can only be done in a browser — the exact URL that opens the right control rather than a shrug towards the homepage.

you › get my company investment ready on fons

    → reads your readiness checklist, drafts the gaps with you, records the metrics,
      tells you which evidence is still missing, and hands you a link to connect Stripe
      so your revenue numbers carry verified provenance instead of your word for it.

Install

You need a Fons account — free at fons.vc/app. A personal profile costs nothing. A company profile is Fons Pro (£49/month per company).

Claude Code — one step

/plugin marketplace add fons-vc/fons
/plugin install fons@fons

That installs the Skill and wires up the MCP server. The first tool call opens a browser consent screen; approve it and you're connected.

Every other agent

One URL, everywhere:

https://fons.vc/mcp

It's a remote Streamable HTTP MCP server with OAuth 2.1, PKCE and dynamic client registration, so in most clients you paste that URL and the browser does the rest — no key, no token, no callback URL to configure.

[mcp_servers.fons]
url = "https://fons.vc/mcp"
auth = "oauth"

{ "mcpServers": { "fons": { "url": "https://fons.vc/mcp" } } }

{ "servers": { "fons": { "type": "http", "url": "https://fons.vc/mcp" } } }

gemini mcp add --transport http fons https://fons.vc/mcp -s user

{ "context_servers": { "fons": { "url": "https://fons.vc/mcp" } } }

{ "mcpServers": { "fons": { "serverUrl": "https://fons.vc/mcp" } } }

The Skill is what turns those tools into good behaviour. Outside Claude Code, copy plugins/fons/skills/fons into your agent's skills directory (~/.claude/skills/fons for Claude Code), or just paste SKILL.md into the conversation — it's plain Markdown and it works as context anywhere.

How it authenticates

No credential ever passes through the chat. Not an API key, not a token, not a password. This is the whole point, so it is worth being precise about:

1. Your agent calls a Fons tool. The server replies 401 with an OAuth challenge.
2. Your agent opens a browser consent screen inside your logged-in Fons session — you approve, as yourself, in a place an agent cannot reach.
3. The agent receives a scoped token and acts as you. Every call is authorized server-side against the same rules the website uses. Row-level security is the boundary, not the client.

The same pattern covers anything that requires proof of ownership. Verifying a LinkedIn account or connecting Stripe returns a bridge URL you open in your own browser — the agent hands you the door; it never holds the key. If you paste a secret at it anyway, the Skill is written to refuse it and tell you to rotate it.

The CLI

npm install -g fons-cli     # or: curl -fsSL https://fons.vc/install.sh | sh   (Node 18+)

fons login                  # OAuth, same browser consent, no tokens to copy
fons profile get
fons profile set --headline "Founder, Acme — B2B infrastructure"
fons company                # your company + data room
fons readiness              # the evidence checklist
fons product set --tagline "…"
fons metrics
fons connectors

The token is stored mode-0600 at ~/.config/fons. Same auth, same server-side authorization, same refusals. See cli/.

Readable without an account

Every public Fons profile ships an agent-readable Markdown twin at the same address — with YAML front-matter and JSON-LD, so a model gets structured facts instead of a scraped page. No auth, no SDK, no API key. Try it right now:

curl https://fons.vc/c/fons-vc.md      # a company (this one is ours)
curl https://fons.vc/p/<slug>.md       # a product
curl https://fons.vc/<handle>.md       # a founder

That's the discovery half of Fons, and it works with every model — no connector, no setup. Paste the URL into ChatGPT, Gemini, Grok, Perplexity, Copilot, or a local Llama, and ask about the company; anything that can read a web page can read a Fons profile. It is also why the profiles are worth keeping accurate: an investor's agent doing background reading will find the .md, not your pitch deck.

The MCP tools in this repo are for your own data. The .md twins are how any agent reads everybody else's.

What it deliberately cannot do

An honest surface is more useful than an omnipotent one. The agent cannot:

• Assert a verification it didn't earn. Verified connections, trust badges and connected metric provenance are written only by a live connector or a proven browser session. An agent can type a number into your data room; it cannot make it verified. That distinction is the product.
• See or invent a score. Fons reports readiness as statuses and bands — never a number. The scoring internals are not exposed to any agent, ever.
• Read your documents. list_documents returns names and dates. File contents never flow through a third-party AI session.
• Forge your history. The company feed is append-only and verification events are server-written, so an audit trail cannot be manufactured from a chat window.
• Exceed your permissions. A view-only teammate gets an honest 403, not a workaround.

Architecture

     your agent                        this repo                     fons.vc
  ┌───────────────┐              ┌────────────────────┐        ┌──────────────────┐
  │ Claude Code   │   skill ───▶ │ SKILL.md           │        │  /mcp            │
  │ claude.ai     │              │ references/        │        │  OAuth 2.1 + PKCE│
  │ Cursor, …     │   tools ───▶ │ .mcp.json ─────────┼───────▶│  ↓               │
  └───────────────┘              │ cli/               │        │  RLS authorizes  │
                                 └────────────────────┘        │  every call      │
        ▲                                                      └────────┬─────────┘
        │                                                               │
        └──────────  browser consent (you, logged in)  ◀────────────────┘

The Skill is instructions; the MCP server is the door; the database is the boundary. A fork of this repo still authenticates as you, through your consent, under your permissions — which is why we can publish it.

Contributing

Issues and pull requests are welcome, particularly on the Skill's guidance: if it gave your agent a bad instruction, that's a bug worth reporting. See CONTRIBUTING.md.

Note that SKILL.md, references/ and cli/ are generated from the Fons monorepo — we accept patches here and land them upstream.

Follow us

• Discord — discord.gg/HVXjkCxgcj. Where we talk about what agents should and shouldn't be trusted to do with a company's own data. Bring the transcript where your agent got it wrong; that's the useful conversation.
• X — @fons_vc.
• Web — fons.vc. Every public profile there has a .md twin, including ours.

Security

Found a vulnerability? Do not open a public issue. See SECURITY.md — report it to admin@fons.vc.

Licence

Apache-2.0. Fons, the Fons logo and fons.vc are trademarks of Fons — the licence grants no rights to them (§6), so a fork must not present itself as Fons.