Skip to main content

portfolio-evidence-mcp

An MCP server that turns a folder of your work - case studies, READMEs, code, reviews, past proposals - into evidence your AI assistant can cite. Ask "which of my projects proves I can do X?" or "answer this screening question from my portfolio" and every claim comes back with the file it came from.

Built for GigBid (an AI-4016 project), usable on its own in Claude Desktop, Cursor or any MCP host.

Install / run

uvx portfolio-evidence-mcp --corpus ~/my-portfolio          # stdio (for desktop hosts)
uvx portfolio-evidence-mcp --corpus ~/my-portfolio --http --port 8101   # Streamable HTTP

Docker: docker build -f infra/docker/mcp-portfolio.Dockerfile . from the GigBid repo.

Claude Desktop (claude_desktop_config.json) / Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "portfolio": { "command": "uvx", "args": ["portfolio-evidence-mcp", "--corpus", "/absolute/path/to/my-portfolio"] }
  }
}

What it exposes

Kind Name What it does
tool (read-only) search_evidence(requirement, k, filters) ranked evidence items with type, source, date and (for proposals) outcome
tool (read-only) match_requirements(job_title, job_text, requirements, k) maps every requirement of a job to evidence in one call; weak requirements are flagged so you never claim them
tool (read-only) get_case_study(id) full text of one item
tool (read-only) list_skills() skills in the portfolio and where they appear
resource portfolio://case/{id}, portfolio://proposal/{id}, portfolio://repo/{slug}, portfolio://index load full items into context
prompt "Answer a screening question from my portfolio" cites evidence ids, refuses to invent experience
prompt "Write an opening line for this job" job post treated as untrusted data
prompt "Which of my projects proves this requirement?" top 3 items with reasons

Standalone mode ranks with BM25 over your files (no API keys, no network). Inside GigBid it uses the measured RAG pipeline (requirement decomposition + hybrid BM25/dense + outcome boost + multi-vector grouping; the cross-encoder re-ranker was dropped because it lowered recall - see the R&D report).

Safety

Read-only: every tool is annotated readOnlyHint: true. Nothing leaves your machine in stdio mode.

MIT licence.

Metadata

Release files for portfolio-evidence-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for portfolio-evidence-mcp 0.1.0
File Size Uploaded Provenance Actions
portfolio_evidence_mcp-0.1.0.tar.gz 9.4 kB Without provenance Details for portfolio_evidence_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for portfolio-evidence-mcp 0.1.0
File Interpreter ABI Platform Actions
portfolio_evidence_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for portfolio_evidence_mcp-0.1.0-py3-none-any.whl

Total release size: 21.7 kB

Release files / portfolio_evidence_mcp-0.1.0.tar.gz

Download URL portfolio_evidence_mcp-0.1.0.tar.gz
Size 9.4 kB
Tags Source
SHA-256 checksum
How to use checksums
227a89ca21110448a42af772bd52efeb986bd893ce3e0a40006e1ab25a1c5863
BLAKE2b-256 checksum
How to use checksums
0432e70645d37d8f9b531b28b47cec0847b6b4d6b7569d6b864ad708139e43bb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / portfolio_evidence_mcp-0.1.0-py3-none-any.whl

Download URL portfolio_evidence_mcp-0.1.0-py3-none-any.whl
Size 12.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cb0854a8b08281848a161bfca73b583490f0d705629befb4cff2d0ae197a791a
BLAKE2b-256 checksum
How to use checksums
04bfc225a8c8182651b714c49358dfc08f5c40aef10cca011aa6664bb8f8651c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for portfolio-evidence-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page