MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

SmartBear MCP

Current Spec Verified Publisher unverified Confidence: Good (0.85)

SmartBear MCP is an MCP server published by smartbear.com with verified support for the current MCP specification revision (2026-07-28). Last verified 2026-08-20.

Does SmartBear MCP support the current MCP specification (2026-07-28)?

Yes. SmartBear MCP has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-20).

Is SmartBear MCP a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for SmartBear MCP (as of 2026-08-20).

How do I connect to SmartBear MCP?

SmartBear MCP is available via a hosted remote endpoint at https://bugsnag.mcp.smartbear.com/mcp, the package npm:@smartbear/mcp, the official MCP Registry under com.smartbear/smartbear-mcp, the source repository at https://github.com/smartbear/smartbear-mcp. Authentication: oauth. Transports: streamable-http.

Does SmartBear MCP support MCP revision 2025-11-25?

Yes. SmartBear MCP supports MCP revision 2025-11-25 (checked 2026-08-20).

Does SmartBear MCP support MCP revision 2026-07-28?

Yes. SmartBear MCP supports MCP revision 2026-07-28 (checked 2026-08-20).

When were SmartBear MCP's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

Which MCP spec revisions does SmartBear MCP support?

SmartBear MCP has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Supported Source

How widely adopted is SmartBear MCP?

Ranked #92 in The MCP 500 with Adoption Index 55.77 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 9,082 API ·

Repository and package signals for SmartBear MCP

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
34
Primary language
TypeScript
License (repository)
MIT
Continuous integration
Present
Tests
Present
Security policy
Present

Declared topics: bugsnag, mcp, mcp-server, open-source, pactflow, portal, reflect, smartbear, swagger, vscode — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
0.37.0
Last published
First published
Releases
55
License (package)
MIT
Maintainers
4
Direct dependencies
10
Unpacked size
1.9 MB
Registry signature
Signed
Build provenance
No attestation

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for com.smartbear/smartbear-mcp at version 0.34.0 - lists remote endpoint https://bugsnag.mcp.smartbear.com/mcp and repository https://github.com/smartbear/smartbear-mcp - accessed
  2. Endpoint probe of https://bugsnag.mcp.smartbear.com/mcp - authorization required on initialize (HTTP 401) - accessed
  3. Official MCP Registry record for com.smartbear/smartbear-mcp re-fetched 2026-08-20 - status active, version 0.37.0, registry updatedAt 2026-08-20 - accessed
  4. Endpoint probe of https://bugsnag.mcp.smartbear.com/mcp on 2026-08-20 - HTTP 401 on initialize, so the OAuth requirement is now endpoint-grounded; the capability set is not observable without credentials - accessed
  5. npm registry metadata for @smartbear/mcp at published version 0.37.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/server, which resolves to @modelcontextprotocol/server@2.0.0 - accessed
  6. Published artifact of @modelcontextprotocol/server@2.0.0, retrieved 2026-08-20 - the artifact declares revision 2026-07-28 and implements the stateless server/discover method. Read from the artifact itself, not from release notes - accessed