GitShow/modelcontextprotocol/servers
modelcontextprotocol

servers

Model Context Protocol Servers

by modelcontextprotocol
Star on GitHubForkWebsitenpm

TypeScript

90.1k stars11.6k forks1.1k contributorsActive · 3d agoSince 20242026.8.31

Meet the team

See all 1063 on GitHub →
olaservo
olaservo541 contributions
tadasant
tadasant239 contributions
cliffhall
cliffhall229 contributions
jspahrsummers
jspahrsummers217 contributions
dsp-ant
dsp-ant160 contributions
jerome3o-anthropic
jerome3o-anthropic121 contributions
maheshmurag
maheshmurag66 contributions
evalstate
evalstate63 contributions

Languages

View on GitHub →
TypeScript82.1%
Python16.9%
Dockerfile1%

Commit activity

Last 12 weeks · 74 commits

Full graph →

Community health

5 of 6 standards met

Community profile →
87
✓README✓License✓Contributing✓Code of Conduct○Issue Template✓PR Template

Recent PRs & issues

Active · Last activity 3d ago
See all on GitHub →
ConnorMoss02
fix(git): refuse to commit when nothing is stagedOpenPR

returns even when nothing is staged. writes a tree from the index unconditionally — GitPython has no gate — and the return string cannot be false: An agent edits files, calls without (or after a that matched nothing), and gets a hash. It reports the work as committed. The working tree is still dirty, still holds the old content, and the repo now carries an empty commit. Nothing in the response distinguishes that from a real commit. itself refuses this: "no changes added to commit". Fix Raise when the index matches HEAD, matching git's default. Two cases git does allow are preserved: the first commit on an unborn branch, where there is no HEAD to compare against an empty merge commit, which git permits while exists — a conflict resolved back to HEAD's content leaves the index matching HEAD, and that commit is legitimate No new parameter: git requires explicitly, so refusing by default matches it. Tests Six, covering both directions. Three assert the refusal (unstaged edit, clean tree, untracked-only) and fail with the source change reverted. Three assert it does not over-refuse (staged deletion, unborn branch, empty merge commit) and pass either way. 53 passed in .

ConnorMoss02 · 2h ago
ConnorMoss02
git_commit reports success and creates an empty commit when nothing is stagedOpenIssue

Describe the bug reports success when nothing is staged. It creates an empty commit and returns a hash, so a caller cannot tell it apart from a real commit. : writes a tree from the index unconditionally; GitPython has no gate. The return string cannot be false. The practical failure: an agent edits files, calls without — or after a whose paths matched nothing — and gets a hash back. It tells the user the work is committed. The working tree is still dirty, still holds the old content, and the repository now carries an empty commit. itself refuses this with "no changes added to commit". To Reproduce Expected behavior Refuse, as does without . Two cases git does permit and that should keep working: the first commit on an unborn branch, and an empty merge commit while is present. Additional context No test covers this; stages a file first. #4761 implements it.

ConnorMoss02 · 2h ago
truecalci
feat(truecalci): add truecalci deterministic compute serverOpenPR

Description Adds the TrueCalci deterministic calculation engine as a Streamable HTTP MCP server located at . TrueCalci provides 24 zero-hallucination mathematical and statutory calculation engines (Income tax brackets, mortgage PITI/PMI, contractor parity, compound schedules, and engineering formulas) executed at Cloudflare Edge. Server Details Server: TrueCalci Repository: https://github.com/truecalci-official/truecalci Homepage: https://truecalci.com Transport: Streamable HTTP () Engines**: 24 Deterministic Tools Motivation and Context AI models frequently hallucinate compound interest schedules, tax brackets, and floating-point math. TrueCalci provides deterministic, IEEE-754 precision math tools to prevent financial and arithmetic hallucinations in AI agents. How Has This Been Tested? Verified via JSON-RPC 2.0 handshake (, , ). Validated live on Claude Desktop and Cursor IDE over Streamable HTTP. Automated unit test suite passing locally and deployed to Cloudflare Edge. Types of changes [x] New feature (non-breaking change which adds functionality) Checklist [x] I have read the MCP Protocol Documentation [x] My changes follows MCP security best practices [x] I have updated the server's README accordingly [x] I have tested this with an LLM client [x] My code follows the repository's style guidelines [x] New and existing tests pass locally [x] I have added appropriate error handling [x] I have documented all environment variables and configuration options

truecalci · 6h ago

Recent fixes

View closed PRs →
henyi-tdca
[TDCA Notice] Congratulations — your project has been selected for the TDCA configuration networkClosedIssue

[TDCA Notice] Congratulations — your project has been selected for the TDCA configuration network Dear maintainers of : We are pleased to inform you that has been selected through TDCA's institutional screening (license: Apache-2.0, verified; protocol-layer fit: official MCP source, TDCA already holds an MCP connector) and is onboarded into the TDCA configuration network at L2-PHY (official node · protocol alignment). Our behavior and boundaries, stated transparently: 1. License compliance: full respect of your Apache-2.0 license; copyright preserved. We integrate by protocol/interface — we do not merge your code into our repository. 2. No core modification: institutional constraints (verifiable attestation / value anchoring / negative-space guardrails) are added at the interface layer only. We do not rewrite your core logic. 3. Brand distinction: any TDCA-compliant integration is clearly labeled "a TDCA node based on modelcontextprotocol/servers" — no blurring of boundaries. 4. Acknowledgments: your project is listed in our ACKNOWLEDGMENTS and public feedback reports. 5. Upstream contribution: any generic fixes we make are contributed back to your repository as pull requests. 6. Royalty, if you ever want it: a royalty ledger exists for integrated open-source nodes (15%, simulated accounting at this stage). Not marketed — we simply inform you the institution exists and how to apply, should you ever wish to. Effective immediately: this notice takes effect upon posting — no reply or waiting period is required for onboarding to proceed. If you have any objection or wish to be removed, reply and we will stop onboarding, remove the node, and return all configuration rights without delay. Thank you for building what you built. — TDCA (henyi-tdca) [TDCA 告知函] 恭喜——贵项目经 TDCA 制度严选,纳入我方配置网络 致 维护团队: 很高兴告知贵项目已通过 TDCA 制度严选(许可:Apache-2.0,已核实;protocol-layer fit: official MCP source, TDCA already holds an MCP connector),将以 L2-PHY (official node · protocol alignment) 纳入 TDCA 配置网络。 我方行为与边界(透明声明): 1. 严格遵守贵项目 Apache-2.0 许可,保留版权声明;以协议/接口方式接入,不合并代码入我方仓库; 2. 不改动贵项目核心逻辑——制度约束(可验证存证/价值锚定/负空间护栏)仅注入于接口层; 3. 合规集成版本明确标注「基于 modelcontextprotocol/servers 的 TDCA 节点」,不模糊品牌边界; 4. 贵项目收录于我方 ACKNOWLEDGMENTS 与公开反哺报告; 5. 我方对通用缺陷的修复将以上游 PR 形式回馈贵仓库; 6. 分润制度存在(开源节点集成记账 15%,当前模拟态)——不推销,仅告知制度存在与申请方式。 即时生效:本告知函发布即生效,纳入无需回复或等待期。若贵方有任何异议,回复即可——我方将立即停止、移除节点并归还全部配置权。 感谢贵方所做的工作。 — TDCA(henyi-tdca)

henyi-tdca · 19h ago
Structured data for AI agents

Repository: modelcontextprotocol/servers. Description: Model Context Protocol Servers Stars: 90104, Forks: 11567. Primary language: TypeScript. Languages: TypeScript (82.1%), Python (16.9%), Dockerfile (1%). Homepage: https://modelcontextprotocol.io Latest release: 2026.8.31 (5d ago). Open PRs: 100, open issues: 387. Last activity: 3d ago. Community health: 87%. Top contributors: olaservo, tadasant, cliffhall, jspahrsummers, dsp-ant, jerome3o-anthropic, maheshmurag, evalstate, baryhuang, marcelo-ochoa and others.

·@ofershap

Replace github.com with gitshow.dev