ESC
↑↓ navigate↵ open

Home / Signal / #010

Signal #010 · 16 November 2026

Sales Compensation's last zero isn't silent anymore. Orb ships an MCP server that's actually documented.

Signal is a weekly note on what actually changed in the commercial software stack (pricing models, agent interfaces, ownership) tagged to the layer of the Agentic Commercial Model it belongs to. A link to the document behind every claim, and no filler to hit a quota: this issue is four items, because four is what the documentation actually supports.

Checked against the 6 November 2026 Agent Access Registry baseline: the eight rows carrying a claimed-undocumented, third-party-only or unclear-write-access status, a targeted check of the registry's “none found” rows most likely to have moved, and a general sweep for MCP and agent-interface news across all 43 tracked vendors and adjacent competitors, re-verified against that dated row. Four rows change below, all re-dated to 16 November 2026.

In this issue

  1. Everstage says Sales Compensation's zero-interface wall just broke. Its own site has no documentation to show for it.
  2. Orb ships the quarter's cleanest MCP server. We missed it in August.
  3. DigitalRoute adds a second Billing & Usage Metering MCP server, with the tool list locked behind a wiki login.
  4. Qwilr trades its third-party MCP wrappers for a first-party one. Still no documentation behind it.
01Layer 5 · Sales Compensation & Incentive Management

Everstage says Sales Compensation's zero-interface wall just broke. Its own site has no documentation to show for it.

Everstage's own platform page now states that its AI assistant, Eva, works “wherever you do: the Everstage web and mobile app, plus Claude, ChatGPT, and Microsoft Copilot through the Everstage MCP server.” It is the first MCP claim we have found anywhere in Everstage's own materials, and unlike CaptivateIQ's “Coming Soon” framing for the same category, it is written in the present tense, as something that already works. We could not find an authentication method, a scope list, a tool schema, or any developer or technical documentation page anywhere on Everstage's site; the only nearby reference is a general mention of “flexible APIs” elsewhere in the integrations section, which does not refer to MCP at all.

Why it matters: Sales Compensation & Incentive Management has been this registry's one clean zero since Signal #001, the single category where no vendor shipped any agent interface at all. That headline technically still holds on the official count, but it is no longer an honest description of the category's marketing: CaptivateIQ and now Everstage both tell prospective buyers an MCP server exists, and neither will show you how to authenticate against one. For a comp or RevOps leader evaluating these tools against an agentic roadmap, the practical answer hasn't moved at all, you still have nothing to build against, but the vendor conversation has: expect SPM/ICM vendors to start citing “MCP support” in deals this quarter the way CRM vendors did a year ago, well before the documentation catches up. Ask for the auth flow, not the slide.

Source: Everstage: Platform · CaptivateIQ: AI Agents (for contrast)

02Layer 6 + 8 · Billing & Usage Metering

Orb ships the quarter's cleanest MCP server. We missed it in August.

Orb publishes a first party, hosted MCP server at mcp.withorb.com over Streamable HTTP — documentation we did not find in our original Aug 21, 2026 audit, which recorded Orb as having no MCP server at all. The server authenticates with an ordinary Orb API key as a bearer token (OAuth is listed as “coming soon,” not yet live) and inherits that key's existing per area scopes, set to none, read or write under Developers > API keys; a call outside the key's scope fails with a permissions error. It exposes more than 100 tools mapped onto Orb's own API, including genuine write operations: create_metric, update_invoice, void_invoice, cancel_subscription, archive_item and delete_alert among them. Event ingestion, amendment and deprecation are explicitly excluded from the tool set.

Why it matters: this is a correction to our own research, not a new launch we can date, and it's the kind of miss worth naming plainly: a fully documented, write capable MCP server sat on Orb's own docs site the whole time our registry called it “none found.” For GTM and billing teams, it also moves the needle on a real decision: usage based billing and metering, a layer that still looked thin on agent interfaces as recently as last week's registry, now has two vendors (Orb and DigitalRoute, below) with a documented MCP server rather than the two it had in August. If your pricing or billing stack runs on Orb, an agent can now action real write operations against it today, scoped the same way any other API key integration would be, with no special new trust model to evaluate beyond the one you already run.

Source: Orb: MCP Server reference

03Layer 6 + 8 · Billing & Usage Metering

DigitalRoute adds a second Billing & Usage Metering MCP server, with the tool list locked behind a wiki login.

DigitalRoute now publishes its own UsageCloud MCP Server, hosted on DigitalRoute's infrastructure in the EU or US with separate regional endpoints. Access runs through OAuth against an allow-listed client callback URL, with each user enrolling a UsageCloud access key once; an administrator must separately grant the tenant an explicit “stream management” scope before any of it works. The documented actions are modest and approval gated by design: the assistant explains and reviews existing streams, recommends fixes, and can draft a new stream from a plain description, but nothing it drafts is built without a human reviewing and approving it first. The page's own “View the Docs” link points to a gated InfoZone (Confluence) wiki page we could not access, so the full tool list and parameter schema remain unverified by us.

Why it matters: DigitalRoute clears our bar for “Official” because the auth model and at least one real scope are both publicly documented on DigitalRoute's own domain, which is more than most “claimed, undocumented” rows in this registry can show. But the gated wiki page is a real gap, not a formality: a vendor or integrator deciding whether to trust this interface can verify the front door but not the full tool surface behind it, which is exactly the kind of partial transparency that looks fine in a sales conversation and matters a great deal in a security review. Billing and usage metering is shaping up as one of the more agent-ready layers on this site; whether that access is cleanly scoped end to end is still something you'll have to ask DigitalRoute directly to confirm.

Source: DigitalRoute: UsageCloud MCP Server

04Layer 3 · CPQ

Qwilr trades its third-party MCP wrappers for a first-party one. Still no documentation behind it.

Qwilr now ships its own first party “Qwilr MCP,” first announced in a Sep 25, 2026 changelog entry and added to the Claude and ChatGPT MCP directories on Nov 3, 2026 — replacing the third party wrappers, such as Zapier MCP, that were the only option we could find as of our Aug 21 check. Qwilr's own product page describes genuinely write capable actions in plain, non-technical English: drafting a proposal from a prompt or from a CRM record (Salesforce is named in one example), archiving old pages, checking proposal performance, and setting up a recurring Slack check-in. None of it comes with a published authentication method, scope list or tool schema, and the page links only to Qwilr's general REST API documentation rather than anything MCP-specific.

Why it matters: this is the same pattern CPQ has shown all year with DealHub, a vendor's own first party MCP server reads as more credible than a third party wrapper, but “first party” and “documented” are two different claims, and this registry only credits the second one. For a sales or RevOps team already running Qwilr, the Zapier-wrapper path you were using before still works the same as it did; whether Qwilr's own branded MCP is safe to point a general purpose agent at, with what scopes and what guardrails, is a question Qwilr hasn't answered publicly yet.

Source: Qwilr: Qwilr MCP · Qwilr: Updates changelog

Registry moves

Four rows re-date this week, to 16 November 2026, all with a grade change. Everstage's Sales Compensation row moves from None found to Claimed, undocumented, after its platform page began describing Eva as working “through the Everstage MCP server” in the present tense, with no documentation behind it; its external API and agent write access columns stay None found. Orb's Billing & Usage Metering row moves from None found to Official, a correction to our own Aug 21 audit that missed its fully documented, write-capable MCP server. DigitalRoute's row in the same category also moves from None found to Official, on the strength of a first party UsageCloud MCP Server with real OAuth and a named scope, though its full tool schema sits behind a gated wiki page we couldn't read. Qwilr's CPQ row moves from Third party only to Claimed, undocumented: a first party Qwilr MCP now exists, but it still ships with no authentication, scopes or schema of its own.

The registry's aggregate figures move with it: 29 of 43 vendors now publish an official MCP server (up from 27), driven by Orb and DigitalRoute. The agent-write-access count holds at 34 of 43, since none of this week's four changes added a write capability beyond what was already documented elsewhere for each vendor. Billing & Usage Metering moves from two of five vendors with an official MCP server to four of five. Sales Compensation & Incentive Management remains the single zero-interface category on the official count, though it is no longer silent: CaptivateIQ and Everstage both now claim an MCP server exists, with zero technical documentation between them.

Signal lands weekly. The registry updates with it.

Layer tagged, evidence linked. If something here is wrong or out of date, tell us and we will re check and re date the row.

Open the registry →