feat(content): add Kudosity MCP server

[t--becker]

Summary

Adds Kudosity as one focused MCP content entry. Kudosity is an MIT-licensed, npm-installable Model Context Protocol server from an Australian messaging provider, giving agents 19 named tools for SMS, MMS and WhatsApp messaging, delivery reports and replies, contact and contact-list management, webhooks, account balance, and runtime API discovery.

Submission path

No linked issue: this is a free-resource content submission using the direct PR path documented in CONTRIBUTING.md. The repository issue form is reserved for product and feature work — product-feature.yml states explicitly "Do not use it for free content submissions; use the PR-first submission flow instead" — and blank_issues_enabled: false means no other issue can be opened.

This supersedes #5577 and #5578. #5577 failed CI on the direct-PR provenance rule (missing submittedBy / submittedByUrl); #5578 fixed that and went fully green, but was closed by the automated issue-link gate.

I also tried the website flow first. heyclau.de/submit reported "Local checks pass" and "This can be submitted, but the private gate will route it to manual maintainer review", but the final button rendered as "Fix blockers" and was unresponsive, with no field flagged across any of the four steps. Worth a look independently of this PR — it's what pushed me to the direct path.

Verification

Addressing the reviewer nit on #5578 that the sources weren't independently checked — all three are publicly verifiable:

Repo	https://github.com/kudosity/mcp — MIT, CI, public
npm	npm view kudosity-mcp → 0.5.0, mcpName: com.kudosity/mcp
Official MCP registry	com.kudosity/mcp → "status":"active", "isLatest":true — domain-verified by a DNS TXT record on kudosity.com, so first-party ownership is independently provable

Disclosure

I work at Kudosity. The disclosure frontmatter field states the commercial relationship, and submittedBy matches the PR author.

Safety and privacy

safetyNotes and privacyNotes are arrays of short strings per content/SCHEMA.md, written against the source rather than the README:

• Send tools deliver real messages to real numbers, bill the connected account, and are irreversible; three further tools are destructive.
• No filesystem, shell or child-process access — the source imports no fs, path, os or child_process.
• Network destinations are named explicitly, including the legacy api.transmitsms.com / api.transmitmessage.com hosts the client actually calls. Those are Burst SMS-era domains; listing only kudosity.com would have been misleading.
• Credentials come from environment variables and reach no log call — the only console output is a startup banner and a missing-key error.

[loopover-orb]

Caution

🛑 LoopOver review result - reject/close recommended

_{Review updated: 2026-07-27 22:56:10 UTC}

1 file · 1 AI reviewer · 1 blocker · CI pending · blocked

🛑 Suggested Action - Reject/Close

Review summary
This adds a single, well-scoped MCP content entry (content/mcp/kudosity-mcp.mdx) for the official Kudosity MCP server, following the mcp category's frontmatter schema with all required fields (installCommand, usageSnippet, copySnippet, configSnippet) present. Sourcing is unusually well-documented: MIT-licensed public repo, npm package, and registry listing with DNS-verified domain ownership, and the PR discloses the author's employment at Kudosity. The diff is confined to one new file with no generated-index or unrelated churn, matching the directory's expected shape for a content submission.

Nits — 5 non-blocking

• Confirm the claimed 19 tools and their exact names in the table match the current README/source at github.com/kudosity/mcp, since this reviewer cannot independently verify the tool list beyond what's asserted in the file.
• The disclosure field is present but somewhat terse given the author is a Kudosity employee; consider making the employment relationship more prominent in the visible body text, not just frontmatter.
• Verify the retrievalSources URLs (raw README, registry search) resolve as claimed before merge.
• Double check installCommand/copySnippet/configSnippet are consistent with each other (configSnippet includes KUDOSITY_API_SECRET while copySnippet and installCommand omit it) — this is intentional per the prerequisites text but worth a maintainer's explicit confirmation.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Why this is blocked

• No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

Decision drivers

• ❌ Code review — 1 blocker (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	⚠️ 1 scoped overlap	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 0 registered-repo PR(s), 0 merged, 0 issue(s).
Contributor context	ℹ️ No public Gittensor match	t--becker; not a blocker.
Improvement	ℹ️ Insufficient signal	risk: low · value: insufficient-signal · LLM: moderate

Manifest validation

• blockedPaths is retired; use settings.hardGuardrailGlobs for path holds.

Review context

• Author: t--becker
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: CSS, HTML, Astro, JavaScript, TypeScript
• Contributor context: Public profile only; not a blocker.
• Related work: Titles/paths share 3 meaningful terms. (issue #5237)

Contributor next steps

• Start here: Review top overlaps.
• Then work through the remaining 2 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/	desktop (light)	before / (light)	after / (light)	—
/	mobile (light)	before / (mobile) (light)	after / (mobile) (light)	—
/	desktop (dark)	before / (dark)	after / (dark)	—
/	mobile (dark)	before / (mobile) (dark)	after / (mobile) (dark)	—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

Scroll preview

Route	Before (production)	After (this PR's preview)
/ (light)	before / (light) (scroll)	after / (light) (scroll)
/ (dark)	—	after / (dark) (scroll)

A short scroll-through clip (desktop) — click either thumbnail to open the full animation. Evidence for scroll-linked behavior a single screenshot can't show.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver is closing this pull request on the maintainer's behalf (No linked issue detected). This is an automated maintenance action — to pursue this change, please open a new pull request with the issues resolved. Closed PRs may be analyzed later to improve review accuracy, but they are not automatically reopened or re-reviewed.