Server Details
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- The-Code-Registry/mcp-server
- GitHub Stars
- 0
See and control every tool call
Available Tools
16 toolscreate_accountTry in Inspector
Creates a new Code Registry account and returns API credentials. Cold starts can cause the first request to time out; retry with backoff. No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Account owner's name. | |
| Yes | Account owner's email. | ||
| team_name | Yes | Team or company name. | |
| integrator_id | No | Optional integrator identifier (used for API key scoping). | |
| integrator_name | No | Optional integrator display name. |
create-code-vaultTry in Inspector
Creates a code vault and queues the initial analysis. IMPORTANT: Always use LOCAL_AGENT (or AGENT) unless the user explicitly requests remote analysis or Docker is unavailable. LOCAL_AGENT runs locally via Docker; source code stays on the machine and only anonymous analysis data is uploaded. A Git repo is only required if you want Git-based insights (git-history, code-contributors). If Git insights are needed, the mounted path must be a standard Git repo containing a .git directory (not a .git file pointing to a worktree). The response includes next_steps.commands that must be executed to start the local agent. Use GIT/FILE_ARCHIVE only when the user provides a reachable URL plus read credentials (username/password or token). Cold starts can cause the first request to time out; retry with backoff. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Vault name. | |
| branch | No | Optional source branch name (GIT only). | |
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| user_id | No | User id (from create_account or get_account). | |
| password | No | Source password or personal access token (required for private GIT repos; must have read access). | |
| username | No | Source username (required for private GIT repos; must have read access). | |
| project_id | No | Project id (from create_project). | |
| source_url | No | Repository or archive URL (required for GIT/FILE_ARCHIVE; ignored for LOCAL_AGENT/AGENT). Must be reachable by the platform. FILE_ARCHIVE accepts .zip/.tar URLs and supported Google Drive/Dropbox links. | |
| description | No | Optional vault description. | |
| source_type | No | Code source type. ALWAYS use LOCAL_AGENT (or AGENT) unless the user explicitly requests remote analysis or Docker is unavailable. LOCAL_AGENT runs locally via Docker; source code stays on the machine and only anonymous analysis data is uploaded. A Git repo is only required for Git-based insights (git-history, code-contributors). If you need those, ensure the mounted path is a standard Git repo containing a .git directory (not a .git file pointing to a worktree). Use GIT/FILE_ARCHIVE only when the user provides a reachable URL plus read credentials (username/password or token). Do NOT attempt GIT without credentials. | LOCAL_AGENT |
create_projectTry in Inspector
Creates a project for a team user. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Project name. | |
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| user_id | Yes | User id (from create_account or get_account). | |
| description | No | Optional project description. |
delete_accountTry in Inspector
Deletes the team account plus all projects and vaults. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| confirm | Yes | Set true to confirm deletion. |
delete-code-vaultTry in Inspector
Deletes a code vault and related analysis data. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| vault_id | Yes | Vault id (from create-code-vault or list_vaults). |
delete_projectTry in Inspector
Deletes a project and its vaults. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| project_id | Yes | Project id. |
get_accountTry in Inspector
Returns the team owner account information. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. |
get-code-vault-reportsTry in Inspector
Returns report URLs (snapshot/comparison) for a vault. Completion rules: if version is 1.0.0, snapshot indicates completion and comparison is null; for versions above 1.0.0, comparison indicates completion. If not ready, retry with exponential backoff (5s, 10s, 20s, 40s, max 60s). This endpoint always returns the latest version only; once reanalysis starts, prior versions are no longer accessible here. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| vault_id | Yes | Vault id (from create-code-vault or list_vaults). |
get-code-vault-resultsTry in Inspector
Returns full facet results and AI insights for a vault. Analysis is async; if status is 'processing', poll with exponential backoff (5s, 10s, 20s, 40s, max 60s). Analysis can be as quick as 20-30 minutes for under 500,000 lines of code. Larger codebases can take much longer, especially with the security scan. Facet meanings are documented in resources://docs/facets; AI Quotient is a code-quality metric (not AI-generated code). AI insights can take a few minutes after analysis completes; if ai_insights is empty, poll again and check ai_insights_status per facet (ready/processing/not_available). This endpoint always returns the latest version only; once reanalysis starts, prior versions are no longer accessible here. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| vault_id | Yes | Vault id (from create-code-vault or list_vaults). |
get-code-vault-summaryTry in Inspector
Returns the latest version/status info for a vault. Analysis is async; if status is 'processing', poll with exponential backoff (5s, 10s, 20s, 40s, max 60s). Analysis can be as quick as 20-30 minutes for under 500,000 lines of code. Larger codebases can take much longer, especially with the security scan. This endpoint always returns the latest version only; once reanalysis starts, prior versions are no longer accessible here. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| vault_id | Yes | Vault id (from create-code-vault or list_vaults). |
get_projectTry in Inspector
Returns a specific project by id. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| project_id | Yes | Project id. |
get_vaultTry in Inspector
Returns a specific vault by id. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| vault_id | Yes | Vault id. |
list_projectsTry in Inspector
Lists all projects for the authenticated team. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. |
list_vaultsTry in Inspector
Lists vaults within a project. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| project_id | Yes | Project id. |
reanalyze-code-vaultTry in Inspector
Creates a new analysis version for an existing code vault using its existing source settings. For LOCAL_AGENT, the response includes next_steps.commands and the local agent must be run again. For GIT/FILE_ARCHIVE, the re-analysis of the original code source is queued automatically. Note: summary/results/report tools always return the latest version only, so reanalysis replaces access to prior version data. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| author | No | Optional author name override. | |
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| comment | No | Optional version comment. | |
| user_id | No | Optional user id for attribution (from create_account or get_account). | |
| vault_id | Yes | Vault id (from create-code-vault or list_vaults). |
rotate_api_keyTry in Inspector
Issues a fresh integrator API key. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for clients that cannot set X-API-Key headers. | |
| integrator_id | No | Optional integrator identifier (defaults to existing integrator or 'default'). | |
| integrator_name | No | Optional integrator display name. |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.