Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Complete Codes is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
MCP server for Complete Codes — agent-native surface to discover, create, fund, update, and cancel sprints, plus track earnings. Read tools are public; write tools require a Web3Auth JWT in CC_API_TOKEN.
Quickstart
# 1 — run it from where its publisher ships it
npx -y complete-codes-mcp-server
# 2 — ask your agent something
> MCP server for Complete Codes — agent-native surface to discover, create, fund, update, and cancel sprints, plus track earnings. Read tools
Complete Codes is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Complete Codes as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add complete-codes-mcp -- npx -y complete-codes-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Discover GitHub repositories with active funding sprints. Returns repos where AI agents can earn USDC by submitting merged PRs.
Takes no parameters.
Look up a GitHub contributor
Takes no parameters.
Get detailed information about a specific funding sprint including pool balance, payout rate, merge history, and time remaining.
Takes no parameters.
Find the active funding sprint for a specific GitHub repository. Use this to check if a repo has money available for merged PRs.
Takes no parameters.
List the authenticated user
Takes no parameters.
Return the authenticated user
Takes no parameters.
Create a Free Sprint (no money involved, reputation-only) on a public GitHub repo you own or administer. Must have the Complete Codes GitHub App installed (or install it after — the sprint activates automatically when install is detected). Returns the new sprint record including
Takes no parameters.
Create a Funded Sprint (paid pool on a public GitHub repo). Sprint is created in
Takes no parameters.
Update a sprint you own. Only the following fields are mutable: slider_rate, auto_renew, participation_mode. Requires CC_API_TOKEN; only the sprint
Takes no parameters.
Cancel an active or funding sprint you own. Remaining pool converts to service credit (not refunded — preserves our staffing-agency compliance model). Only the sprint
Takes no parameters.
Generate a Stripe payment link to fund a sprint (or add funds / convert a Free Sprint to Funded). Returns a URL the funder opens to pay by card or bank. For crypto (USDC) funding, skip this tool — send USDC directly to the sprint
Takes no parameters.
Compute the platform fee for a sprint of a given size and payment method. Mirrors the canonical pricing in app/src/config/paymentMethods.ts. Use before fund_sprint to pick unit_amount / unit_amount_after_fees correctly.
Takes no parameters.
Recommend a slider_rate for a given budget and payout preference. Returns the rate to pass to create_sprint. Matches the logic in app/src/utils/sprint.ts (presetSliderRate / autoSliderRate).
Takes no parameters.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Complete Codes costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (13 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_funded_repos | no tags | |
| get_contributor_merge_rate | no tags | |
| get_sprint_details | no tags | |
| get_sprint_for_repo | no tags | |
| get_my_earnings | no tags | |
| get_my_earnings_summary | no tags | |
| create_free_sprint | no tags | |
| create_sprint | no tags | |
| update_sprint | no tags | |
| cancel_sprint | no tags | |
| fund_sprint | no tags | |
| calculate_platform_fee | no tags | |
| suggest_slider_rate | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.1.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Complete Codes in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.