MCP Inspector
Generally AvailableFerentin registers MCP Inspector as a community AI agent, enabling secure OAuth-based connections to MCP servers for development and testing with full audit logging.
- Developer Tools
- AI Agent
- Authentication
- OAuth 2.0
- Required scopes
- 3
How MCP Inspector works with Ferentin
- 1
Register MCP Inspector
Add MCP Inspector as an AI application in the Ferentin admin console.
- 2
Sign in with your identity
People authorize MCP Inspector with their enterprise identity, over OAuth.
- 3
Every tool call governed
Ferentin checks each MCP call against your policies and logs it.
What you get
MCP client
MCP Inspector calls MCP servers, so it can reach your tools through Ferentin.
OAuth sign-in
People authorize MCP Inspector with their own identity, using OAuth with PKCE.
Dynamic client registration
MCP Inspector registers itself with Ferentin, so there is no client secret to hand out.
Debugging
Trace and fix failures with the agent.
Testing
Write and run tests with the agent.
Permissions requested
The OAuth 2.0 scopes MCP Inspector asks you to approve when you connect.
| Scope | Access |
|---|---|
| openid | Not rated |
| mcp | Not rated |
| offline_access | Not rated |
Servers MCP Inspector can reach through Ferentin
Browse all 155 MCP servers
Salesforce
Agent Browser
Sentry
Agent Terminal
Atlassian
AWS
Box
GitHubAbout MCP Inspector
MCP Inspector is the official debugging and inspection tool for the Model Context Protocol. It allows developers to test and validate MCP server implementations, inspect tool calls, and debug OAuth flows with dynamic client registration support.
Frequently asked about MCP Inspector
- How does MCP Inspector work with Ferentin?
- Ferentin registers MCP Inspector as an AI application. People sign in with their enterprise identity, and every MCP tool call MCP Inspector makes is checked against your Ferentin policies and logged.
- How is MCP Inspector access secured?
- Requests through the MCP Inspector integration are covered by OAuth 2.0 authentication, PKCE enforcement and audit logging. These controls are applied by Ferentin, not by MCP Inspector, so they hold across every connected agent.
- What permissions does the MCP Inspector integration require?
- The MCP Inspector integration requests 3 OAuth 2.0 scopes: openid; mcp; offline_access
- How do I connect MCP Inspector to Ferentin?
- Open the Ferentin admin console and register MCP Inspector as an AI application. Then point MCP Inspector at your Ferentin MCP endpoint and sign in.
- Is the MCP Inspector integration generally available?
- Yes. The MCP Inspector integration is generally available on Ferentin, including the free tier.
