io.github.STR-Consulting/pacer-mcp
OCI · GHCR.IO/STR-CONSULTING/PACER-MCP:1.0.0
Pacer revenue-management API as MCP tools: portfolios, pacing, market metrics, Guesty, briefs.
Available components
Last scanned (4 hours ago)
Scores higher than 75% of OCI servers
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 105 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 2767 tokens (~98/item across 28 items; 28 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_billed_units_by_rm" implies "rm" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.77 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 93. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed oci/ghcr.io/str-consulting/pacer-mcp:1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_portfolio_integration ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_billed_units_by_rm ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_client_health_brief ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_client_health_scoring_config ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_managed_units_by_rm ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_billed_units ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_integration_secrets ~97
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_market_metrics ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_metrics_ytd ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_pacing ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_team ~94
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricelabs_notes ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricelabs_overrides ~97
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricelabs_tags ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guesty_pricing_config ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guesty_reservation_promotions ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health_check ~92
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_briefable_portfolios ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_client_health_briefs ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_managed_keydata_units ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_portfolio_integrations ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_portfolio_new_listings ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_portfolio_reservations ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_portfolio_teams ~95
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_portfolio_units ~94
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_portfolio_integration_secrets ~97
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upsert_client_health_brief ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upsert_intel_brief ~96
RETIRED. This standalone pacer-mcp server (PAT over stdio) is RETIRED and no longer reaches the Pacer API. Use the in-process Pacer MCP connector built into core instead — it is offered as the hosted "Pacer" connector on claude.ai / Claude Cowork (tools appear as mcp__…Pacer__…). Remove this standalone server from your MCP client config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.STR-Consulting/pacer-mcp server?
io.github.STR-Consulting/pacer-mcp runs locally as a container image, launched with docker run --rm -i -e PACER_CORE_URL -e PACER_CORE_TOKEN ghcr.io/str-consulting/pacer-mcp:1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/str-consulting/pacer-mcp:1.0.0
claude mcp add str-consulting-pacer-mcp -- docker run --rm -i -e PACER_CORE_URL -e PACER_CORE_TOKEN ghcr.io/str-consulting/pacer-mcp:1.0.0
This image reads PACER_CORE_URL and PACER_CORE_TOKEN. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the io.github.STR-Consulting/pacer-mcp server?
io.github.STR-Consulting/pacer-mcp is listed in the public MCP registry as io.github.STR-Consulting/pacer-mcp. Pacer revenue-management API as MCP tools: portfolios, pacing, market metrics, Guesty, briefs. This page covers its container image (ghcr.io/str-consulting/pacer-mcp:1.0.0).
Is the io.github.STR-Consulting/pacer-mcp server safe to use?
io.github.STR-Consulting/pacer-mcp scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.STR-Consulting/pacer-mcp server expose?
io.github.STR-Consulting/pacer-mcp exposes 28 tools: create_portfolio_integration, get_billed_units_by_rm, get_client_health_brief, get_client_health_scoring_config, get_managed_units_by_rm, and 23 more. Their descriptions and schemas cost roughly 2,675 tokens of context every time the server is loaded.
Is the io.github.STR-Consulting/pacer-mcp server still maintained?
io.github.STR-Consulting/pacer-mcp is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.STR-Consulting/pacer-mcp server under?
io.github.STR-Consulting/pacer-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.STR-Consulting/pacer-mcp server?
VerifyMCP ran 12 checks on io.github.STR-Consulting/pacer-mcp, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.STR-Consulting/pacer-mcp: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.