Credential Camp

com.credentialcamp.appPublished by app.credentialcamp.comOfficial publisherv1.1.0Updated Oct 29, 2026

Tenant-scoped credentials, training and business records with owner-controlled write approvals.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint for Credential Camp that gives an assistant tenant-scoped access to credentials, training and business records with owner-approved writes.

What you can do
  • Access tenant-scoped credentials, training records and business records through the hosted Credential Camp endpoint.
  • Writes are subject to owner-controlled approval rather than being applied directly.
  • No tool list is published, so the exact operations available are not documented in the registry entry.
When to use it
Consider it when an assistant needs to read or propose changes to credential, training or business records held in Credential Camp for a specific tenant, with changes gated by an owner's approval.
Requirements
A remote MCP connection to the hosted endpoint at app.credentialcamp.com over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server handles credentials, so treat anything it returns as sensitive. Writes are gated by owner approval, but confirm who holds that approval role before relying on it. The tool list is not published, so review the actual tools after connecting.

Installation

In SourceWeft

  1. Open Credential Camp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.credentialcamp.app%2Fcredential-camp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "credential-camp": {
      "type": "http",
      "url": "https://app.credentialcamp.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.