@vanmoose/mcp-server

MCPcommunity
v1.4.0Van MooseMITUpdated todaynpmGitHub

211 MCP tools across 76 developer APIs (192 VanMoose + Truncus, obqo, TenScore, WebIntel) — one server, one bring-your-own-key per service

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
21Downloads/wk
todayLast update
Reads these credentials
  • VANMOOSE_API_KEYAPI keyoptional

    Your VanMoose API key from vanmoose.cc/dashboard

  • TENSCORE_API_KEYAPI keyoptional

    TenScore API key (enables 5 TenScore analytics tools)

  • TRUNCUS_API_KEYAPI keyoptional

    Truncus API key (tr_live_…, from truncus.co/dashboard/settings/api-keys; enables 8 Truncus email tools)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorVan Moose
LicenseMIT
Version1.4.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv1.4.0 · todayHow well does this scan work?
EvalsNone
IndexedOct 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev1.4.0 · 14h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

obqo_list_studentsList students in your obqo organization with optional filters (programme, status, search). Returns roster rows with id, name, email, programme, status, and coach assignment. Use for triage or to find a student before booking a session.

List students in your obqo organization with optional filters (programme, status, search). Returns roster rows with id, name, email, programme, status, and coach assignment. Use for triage or to find a student before booking a session.

No input schema was published for this tool.

obqo_list_sessionsList coaching sessions with optional filters by coach, student, or date range. Returns each session with date, type, format, coach, student, and no-show flag.

List coaching sessions with optional filters by coach, student, or date range. Returns each session with date, type, format, coach, student, and no-show flag.

No input schema was published for this tool.

obqo_list_career_signalsList career signals (alumni job changes, promotions, profile updates) for your organization. Each signal carries student, type ('job_change' / 'promotion' / 'profile_update'), source ('self' / 'coach' / 'import'), confidence, and review status.

List career signals (alumni job changes, promotions, profile updates) for your organization. Each signal carries student, type ('job_change' / 'promotion' / 'profile_update'), source ('self' / 'coach' / 'import'), confidence, and review status.

No input schema was published for this tool.

obqo_get_analyticsGet aggregated analytics for one of the analytics tabs: 'coaching' (sessions + coverage), 'events' (attendance + ratings), 'career' (placement rate + time-to-employment), 'engagement' (engagement vs placement), or 'placement-matrix' (timing breakdown). Filters mirror the dashboard UI.

Get aggregated analytics for one of the analytics tabs: 'coaching' (sessions + coverage), 'events' (attendance + ratings), 'career' (placement rate + time-to-employment), 'engagement' (engagement vs placement), or 'placement-matrix' (timing breakdown). Filters mirror the dashboard UI.

No input schema was published for this tool.

truncus_validateRun all the pre-send checks (suppression, domain health, content quality, deliverability score) without sending. Returns a `confidence` score, blocking `errors`, and non-blocking `warnings`. Use before truncus_send to catch issues early when generating email content from an LLM.

Run all the pre-send checks (suppression, domain health, content quality, deliverability score) without sending. Returns a `confidence` score, blocking `errors`, and non-blocking `warnings`. Use before truncus_send to catch issues early when generating email content from an LLM.

No input schema was published for this tool.

truncus_get_emailLook up a specific email by its Truncus ID. Returns the full send record plus the event timeline (queued, sent, delivered, opened, clicked, bounced, complained). Use to verify outcome of an earlier send, debug deliverability issues, or read tracked engagement.

Look up a specific email by its Truncus ID. Returns the full send record plus the event timeline (queued, sent, delivered, opened, clicked, bounced, complained). Use to verify outcome of an earlier send, debug deliverability issues, or read tracked engagement.

No input schema was published for this tool.

truncus_list_eventsReturn the chronological event timeline for a single email — every state transition SES (or the configured provider) reports back. Use when the agent needs to surface "why did this email fail" or to wait for a specific event type.

Return the chronological event timeline for a single email — every state transition SES (or the configured provider) reports back. Use when the agent needs to surface "why did this email fail" or to wait for a specific event type.

No input schema was published for this tool.

truncus_get_statsAggregated send/open/click/bounce/complaint counts across the account for a configurable lookback window. Use to surface "how is my domain doing" answers, or to gate further sends on bounce-rate health.

Aggregated send/open/click/bounce/complaint counts across the account for a configurable lookback window. Use to surface "how is my domain doing" answers, or to gate further sends on bounce-rate health.

No input schema was published for this tool.

truncus_list_domainsList all domains attached to the account with verification status and per-domain stats (sent, bounce rate, complaint rate, paused state). Use this before truncus_send to confirm which `from` addresses are usable.

List all domains attached to the account with verification status and per-domain stats (sent, bounce rate, complaint rate, paused state). Use this before truncus_send to confirm which `from` addresses are usable.

No input schema was published for this tool.

truncus_check_suppressionCheck whether a given recipient is on the account-wide (or tenant-scoped) suppression list. Returns the suppression record if present, or 404 if the address is clean. Use to short-circuit sends to addresses that have previously bounced, complained, or unsubscribed.

Check whether a given recipient is on the account-wide (or tenant-scoped) suppression list. Returns the suppression record if present, or 404 if the address is clean. Use to short-circuit sends to addresses that have previously bounced, complained, or unsubscribed.

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

211 MCP tools across 76 developer APIs (192 VanMoose + Truncus, obqo, TenScore, WebIntel) — one server, one bring-your-own-key per service

Keywords
mcpanthropicclaudetoolsapideveloperdeveloper-toolsvanmoosemodel-context-protocol
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-18 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.