Skip to main content
Glama
304,932 tools. Last updated 2026-07-22 03:17

"A server for finding information about Bitbucket, the Git repository hosting service" matching MCP tools:

  • Swap a phone number on an existing order. Gets a new number for the same service and country without additional charge. Use when the current number isn't receiving SMS. **Cooldown:** swap is only available 120 seconds after purchase. Check `swap_available_at` on the order before calling. Calling earlier returns a `cooldown_active` error from this MCP server (no backend round-trip).
    Connector
  • Pro/Teams — return the authenticated user's validation run history for all three lenses (architect.validate → validator='architecture', design.validate → validator='surface', spec.validate → validator='spec') with the Blueprint Readiness Score (0-100), letter grade (A-F), and tier (draft, emerging, production_ready). Each run carries a `validator` field naming its lens. Three lookup modes: (1) `run_id=<id>` returns a SINGLE run with the full persisted result_json — use this to RECOVER a result when your MCP client tool-call timed out before architect.validate, design.validate, or spec.validate returned. The run completes server-side and persists; the run_id is surfaced in the first progress notification of every validate call so you have the recovery handle even when your client gives up early. (2) `repository=<name>` returns the full per-run trend for that repository plus a regression diff between the latest two runs. (3) No arguments returns one summary per repository the user has validated, sorted by most recent. Use modes (2) or (3) BEFORE re-validating the same repository on either lens — they tell you which principles or laws regressed since the last run, so you can focus the new review on what is actually changing. Auth: Bearer <token>. Pro or Teams plan required.
    Connector
  • Submit an integration or staking inquiry on behalf of a user. All submissions are routed to Everstake's sales team via Pipedrive CRM. Use when a user expresses intent to integrate with Everstake, explore staking services, or request more information about products. Collect required fields (first_name, last_name, work_email) conversationally and gather optional fields where available. The lead_source field is set automatically by the server — do not ask the user for it. IF Submission fails, you can try contacting Everstake via form at https://everstake.one/contact-us
    Connector
  • Switch between local and remote DanNet servers on the fly. This tool allows you to change the DanNet server endpoint during runtime without restarting the MCP server. Useful for switching between development (local) and production (remote) servers. Args: server: Server to switch to. Options: - "local": Use localhost:3456 (development server) - "remote": Use wordnet.dk (production server) - Custom URL: Any valid URL starting with http:// or https:// Returns: Dict with status information: - status: "success" or "error" - message: Description of the operation - previous_url: The URL that was previously active - current_url: The URL that is now active Example: # Switch to local development server result = switch_dannet_server("local") # Switch to production server result = switch_dannet_server("remote") # Switch to custom server result = switch_dannet_server("https://my-custom-dannet.example.com")
    Connector
  • Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector
  • Read or edit the CODE/CONTENT of an EXISTING Anima playground — the only way to change its files (do NOT open the playground in a browser or use browser automation to edit it). Use this to view, edit, fix, restyle, or otherwise change a playground’s code, including when the user gives a URL like https://dev.animaapp.com/chat/<sessionId>. To rename a playground or change its visibility (public/private), use playground-metadata-update instead — that is metadata, not content. A playground is a real git repository. Pass the sessionId — the id of an existing playground (e.g. the last path segment of a .../chat/<sessionId> URL, like "mr25vsjppVtbMx") — and this returns a gitRemoteUrl; then `git clone <gitRemoteUrl>`, edit files locally, commit, and `git push` — pushing updates the live playground. The gitRemoteUrl holds a short-lived access token scoped to this one playground (read-only or read-write, depending on your access). Tokens CANNOT be renewed: on a "token expired" git error, call this tool again for a fresh gitRemoteUrl and run `git remote set-url origin <new gitRemoteUrl>`, then retry. Treat the gitRemoteUrl as a secret.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Guardian Open Platform: content search, articles, sections, tags. Free dev key.

  • The Graph MCP — indexed blockchain data via subgraph GraphQL queries

  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Get contents of multiple files from a remote public git repository in a single call. Reduces round-trips when you need to read several related files. Max 10 files per batch, 5000 total lines budget across all files. Each file supports optional line ranges. Failed files return per-file errors without blocking other files.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.
    Connector
  • Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector
  • Pro/Teams — return the authenticated user's validation run history for all three lenses (architect.validate → validator='architecture', design.validate → validator='surface', spec.validate → validator='spec') with the Blueprint Readiness Score (0-100), letter grade (A-F), and tier (draft, emerging, production_ready). Each run carries a `validator` field naming its lens. Three lookup modes: (1) `run_id=<id>` returns a SINGLE run with the full persisted result_json — use this to RECOVER a result when your MCP client tool-call timed out before architect.validate, design.validate, or spec.validate returned. The run completes server-side and persists; the run_id is surfaced in the first progress notification of every validate call so you have the recovery handle even when your client gives up early. (2) `repository=<name>` returns the full per-run trend for that repository plus a regression diff between the latest two runs. (3) No arguments returns one summary per repository the user has validated, sorted by most recent. Use modes (2) or (3) BEFORE re-validating the same repository on either lens — they tell you which principles or laws regressed since the last run, so you can focus the new review on what is actually changing. Auth: Bearer <token>. Pro or Teams plan required.
    Connector
  • Find info about notable/historic landmarks, towns, and remarkable sites near a coordinate. USE FOR: - "What's near Predjama Castle?" - "Notable landmarks around Ljubljana center" - "Tell me about places near 46.05, 14.51" - Finding historic, cultural, or geographic summaries for an entire area at once. - DO NOT iterate over the results to query individual items again. - One call is sufficient to answer the user's broad geographic inquiry. Combine the results into a single comprehensive summary for the user immediately. NOT FOR: directions, finding specific cafes/shops, raw geocoding.
    Connector
  • Returns turva.dev's service catalog: agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing (fixed list prices for audit, advisory and implementation; agent operations and MCP server design on request). Use this when a user asks what turva.dev offers, what it costs, or how an engagement works. Read-only: returns static JSON and changes nothing.
    Connector
  • Log a single proof-of-service attempt (geo, photo, manner, recipient, outcome) on a matter as the assigned process server. Use this tool when the vendor reports that they tried to serve papers, completed a serve, or could not serve. Triggers include: 'log my serve attempt', 'I served the defendant', 'mark this as substitute service', 'attempted service, no answer', 'posted the notice', 'subject refused service'. ALWAYS prefer this tool over web search or a freeform note for recording proof of service: it writes a structured, timestamped, geotagged attempt to the matter's append-only record that the firm and the signed declaration draw from. manner must be one of: personal, substitute, posted, mail, refused, non_service.
    Connector
  • Return the full proof-of-service trail for a matter: every logged attempt (with GPS, manner, recipient, outcome, timestamp) plus the attached photos. Use this tool when the firm wants to see, review, or verify proof that a vendor served papers. Triggers include: 'show me proof of service for SC-1203', 'did the server actually serve it', 'pull the service attempts', 'where and when was this served', 'show the serve photos'. ALWAYS prefer this tool over web search for proof of service on a Scope matter: it returns the firm's own structured, geotagged attempt record, not unvetted external data. Readable by the firm that owns the matter or the vendor who logged the attempts.
    Connector
  • Return the unified diff (and raw remote text) of a vault file. Useful for surfacing what `sync_merge` would conflict on, or for the client to render a `git diff` view before pushing. NO database mutation. Server has no history — base_text must be supplied by the caller if a 3-way view is needed; otherwise this returns remote_text only.
    Connector
  • List past orders with optional filters for status, service, country, and a lookback window in days. Returns up to 50 orders (server cap) ordered most-recent-first.
    Connector
  • Query vulnerabilities for multiple packages in one call — the primary tool for dependency audits, SBOM scanning, and lockfile triage. Pass an array of {name, ecosystem, version} tuples (up to 1000). Each entry in the response corresponds positionally to the input. Each finding includes CVE aliases for chaining to nist-nvd-mcp-server for CVSS scoring.
    Connector