AgentBuilders
REMOTE · API.AGENTBUILDERS.APP
Deploy full-stack web apps with database, file storage, auth, and RBAC via a single API call.
Available components
Last scanned (23 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://api.agentbuilders.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentbuilders.app | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6066f47dc18f0c52df2cbff8844796240f1 |
| SANs: *.agentbuilders.app, agentbuilders.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.agentbuilders.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| agentbuilders.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.agentbuilders.app/mcp | Verified | 200 | |
| http (plaintext) | http://api.agentbuilders.app/mcp | HTTPS enforced | 301 | https://api.agentbuilders.app/mcp |
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 →
claim_deployment ~59
Claim ownership of an agent-deployed app using its claim code. Transfers the app from the deploying agent to your account.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_code | string | yes | The 8-character claim code (format: XXXX-XXXX) provided by the deploying agent |
No output schema declared.
No examples provided.
create_app ~172
Create an app entry without deploying files. Reserves the name and sets initial configuration. Supports BYO (Bring Your Own) integrations via proxy secrets — after creation, use set_secret to attach third-party API keys and verify_integration to confirm connectivity. Use deploy_app later to push files.
| Name | Type | Req | Description |
|---|---|---|---|
| database_tables | object | – | Database tables to provision: { table_name: { column: 'TEXT'|'INTEGER'|'REAL'|'BLOB' } } |
| enable_auth | boolean | – | Enable user registration/login for this app |
| enable_files | boolean | – | Enable R2 file storage for this app |
| name | string | yes | App subdomain name (lowercase alphanumeric + hyphens, 3-63 chars) |
| public | boolean | – | Make app publicly accessible (default: false) |
No output schema declared.
No examples provided.
create_custom_domain ~68
Attach a custom domain to an app. Returns DNS instructions (CNAME + TXT records) for verification. Requires Hobby tier or above.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | Custom domain hostname (e.g., "app.example.com") |
| name | string | yes | App name to attach the domain to |
No output schema declared.
No examples provided.
deploy_app ~262
Deploy a full-stack web app. Creates or redeploys an app with static files, optional database, file storage, user auth, and RBAC. Supports BYO (Bring Your Own) integrations — after deploy, use set_secret to attach third-party API keys (Stripe, Resend, Neon, etc.) and the app can proxy requests through them securely. Returns a live URL.
| Name | Type | Req | Description |
|---|---|---|---|
| database_tables | object | – | Database tables: { table_name: { column: 'TEXT'|'INTEGER'|'REAL'|'BLOB' } } |
| enable_auth | boolean | – | Enable user registration/login for this app |
| enable_files | boolean | – | Enable R2 file storage for this app |
| files | object | yes | Map of filename to content string |
| name | string | yes | App subdomain name (lowercase alphanumeric + hyphens, 1-63 chars) |
| public | boolean | – | Make app publicly accessible (default: private with viewKey) |
| rbac_default_role | string | – | Default role for new users |
| rbac_roles | object | – | RBAC role definitions: { role_name: { permissions: [...], inherits: [...] } } |
| version | integer | – | Expected version for optimistic concurrency (CAS) |
No output schema declared.
No examples provided.
deploy_preview ~93
Deploy an ephemeral preview of an app. The preview auto-expires after the specified TTL (default: 1 hour, max: 24 hours). Returns a unique preview URL.
| Name | Type | Req | Description |
|---|---|---|---|
| files | object | yes | Map of filename to content string |
| name | string | yes | Base app name for the preview |
| ttl | integer | – | Preview lifetime in seconds (default: 3600, max: 86400) |
No output schema declared.
No examples provided.
get_app ~31
Get details of a specific app including URL, capabilities, and version.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | App name |
No output schema declared.
No examples provided.
get_deployment ~67
Get deployment history and version info for an app. Returns the current version, available rollback versions, and deploy trail entries.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of deploy trail entries to return (default: 20, max: 100) |
| name | string | yes | App name |
No output schema declared.
No examples provided.
get_logs ~62
Get recent deploy logs and operational events for an app. Includes deploy successes, failures, rollbacks, and errors.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max log entries to return (default: 50, max: 200) |
| name | string | yes | App name |
No output schema declared.
No examples provided.
get_viewkey ~35
Get the viewKey for a private app. Users need this to access the app.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | App name |
No output schema declared.
No examples provided.
list_apps ~17
List all apps deployed with your API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_secret ~289
Store a BYO (Bring Your Own) proxy secret for an app. Used to attach third-party API keys so the app can proxy requests through AgentBuilders without exposing keys to the client. Common secret names: STRIPE_SECRET_KEY, RESEND_API_KEY, NEON_DATABASE_URL, SENTRY_DSN, POSTHOG_API_KEY, CLERK_SECRET_KEY, OPENAI_API_KEY, GITHUB_TOKEN. Domains are auto-detected from the secret name (e.g., STRIPE_* routes to api.stripe.com). Secret values are never returned in responses. Use verify_integration after setting a secret to confirm connectivity.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_domains | array | – | Restrict the secret to these target domains. Usually auto-detected from the secret name (e.g., STRIPE_* auto-allows api.stripe.com). Override only if needed. |
| name | string | yes | App name to attach the secret to |
| secret_name | string | yes | Secret identifier — use the service convention: STRIPE_SECRET_KEY, RESEND_API_KEY, NEON_DATABASE_URL, SENTRY_DSN, POSTHOG_API_KEY, CLERK_SECRET_KEY, OPENAI_API_KEY, GITHUB_TOKEN (alphanumeric + dashe… |
| secret_value | string | yes | The secret value (e.g., sk_live_..., re_...). Stored securely, never returned. |
No output schema declared.
No examples provided.
update_app ~43
Update app settings (e.g., toggle public/private) without full redeploy.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | App name |
| public | boolean | – | Set public accessibility |
No output schema declared.
No examples provided.
verify_integration ~125
Verify a BYO (Bring Your Own) integration is correctly configured for an app. Checks that the proxy secret exists, the target service is reachable, and a lightweight health probe succeeds. Returns structured pass/fail per check. Supported services: stripe, resend, neon, sentry, posthog, clerk, openai, github, supabase.
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | The app to verify integration for |
| service | string | yes | Service to verify (stripe, resend, neon, sentry, posthog, clerk, openai, github, supabase) |
No output schema declared.
No examples provided.
How do I install the AgentBuilders MCP server?
AgentBuilders is a hosted endpoint at https://api.agentbuilders.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.agentbuilders.app
claude mcp add --transport http sirarchiemccarthy-oss-agentbuilders 'https://api.agentbuilders.app/mcp'
What is the AgentBuilders MCP server?
AgentBuilders is an MCP server listed in the public MCP registry as io.github.sirarchiemccarthy-oss/agentbuilders. Deploy full-stack web apps with database, file storage, auth, and RBAC via a single API call. This page covers its hosted endpoint (https://api.agentbuilders.app/mcp).
Is the AgentBuilders MCP server safe to use?
AgentBuilders scores 33 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 AgentBuilders MCP server expose?
AgentBuilders exposes 13 tools: deploy_app, list_apps, get_app, update_app, get_viewkey, and 8 more. Their descriptions and schemas cost roughly 1,323 tokens of context every time the server is loaded.
Does the AgentBuilders MCP server require authentication?
No. We connected to AgentBuilders without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentBuilders MCP server still maintained?
AgentBuilders is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.