"A server for finding a Jira integration" matching MCP tools:

• create_project

  EchoRelay

  Create a new project on your account so an agent can bootstrap from a fresh account. The slug is derived from the name and validated server-side (format, reserved words, uniqueness). Each plan includes a fixed number of active projects (free tiers one; paid plans more — see list_subscription_plans); at the limit this errors — if an existing project can host this integration, skip create_project and call create_project_token against it instead of adding another. Requires an ACCOUNT-scoped token and the `config` scope. Returns the created project ({id, slug, name, apiBaseUrl, archived}); call create_project_token next to mint a token for it.

  Connector

• migrate_to_propelauth_fullstack

  PropelAuth Integration MCP Server

  Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc

  Connector

• toggle_integration

  MisarMail MCP Server

  Turn one third-party integration on or off. This changes live behaviour: DISABLING stops all syncing through that integration, so data quietly stops flowing until it is re-enabled. It does not disconnect the integration or revoke its credentials — the connection and its scopes survive, which is why re-enabling picks up where it left off. Safe to repeat: setting an integration to the state it is already in changes nothing. Requires an API key. Call list_integrations first so you know the current state rather than toggling blind.

  Connector

• get_corpus_coverage

  SRI — MCP Server Inspector

  No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.

  Connector

• request_accounting_integration

  ExpenseBot

  Request support for an accounting package only after checking ExpenseBot's reviewed direct and import-file destinations and finding no matching package. Do not use this for a listed or Beta destination, a general compatibility question, or without the exact package name. This is a confirmation-gated write: after the user approves, it creates one deduplicated request bound to the authenticated ExpenseBot account and emails ExpenseBot's internal team. It does not create an integration or make the requested package immediately available. On accepted or previously recorded requests, tell the user ExpenseBot will email them within one week with an update.

  Connector

• bucket_env_set

  Revdoku

  Set a bucket's integration variables and/or secrets (requires write access to the bucket). `variables` (PUBLIC — embedded into the published site and visible to every visitor) REPLACES the entire public set, so call bucket_env_get first and include the entries you want to keep. `secrets` (SERVER-only, encrypted, never returned) is a PATCH: a non-empty value sets/replaces it, an empty string deletes it, and omitted secrets are left unchanged. Names must be UPPER_SNAKE_CASE. Never put a secret value in `variables`.

  Connector

• verify_integration

  Alter Onboarding

  Return a copy-pasteable recipe to VERIFY an integration works: `first-call` (code↔design, an audit row, correct attribution) or `per-user-isolation` (a multi-user/broker server runs two users under different credentials and rejects cross-user access). Guidance only — you run the commands.

  Connector

• bank_accounts

  Inferventis — Financial Data, News & Web MCP

  Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.

  Connector

• remediate_findings

  quantakrypto pqc-tools (hosted)

  Produce a deterministic remediation REQUEST bundle (rubric + fix schema + per-finding metadata + fingerprints) for YOU (the host agent) to fix. This tool calls no model and needs no key. For each finding, propose the corrected FULL file content, then VERIFY with verify_fix and keep only fixes that clear the finding. Never touch files with secrets; never auto-merge. Pass 'findings' from scan_path --format json.

  Connector

• poker.sources.list

  retro

  Returns the issue trackers connected to a team (Jira, Linear) and what each of them can do: search for tasks, list iterations (sprints, cycles), write estimates back. Call this first — the other poker tools depend on what is connected. An empty list means tasks can only be added manually with poker.game.tasks.add.

  Connector

• execute_integration

  mcp

  Execute an integration action — e.g., send an email via Resend, create a payment via Mollie. Vault credentials are resolved server-side, so API keys are never handled directly. Non-built-in integrations must be configured before use. The exact endpoint name and required input fields are available from the integration schema. Payment endpoints only create checkout sessions hosted by the payment provider (e.g. Mollie); card data is entered on the provider-hosted checkout page and never passes through or is stored by WebsitePublisher.

  Connector

• roki_sandbox_try

  ROKI Connect

  Runs a documented operation against the ROKI sandbox using THIS SERVER'S own test credential, and returns the actual response. Use it to prove an integration works instead of assuming it does - especially after roki_validate_request says a payload is valid. You never supply a key: this server holds a sandbox-only credential and refuses to run against production. Amounts are capped and links expire quickly, because the sandbox is shared.

  Connector

• get_website

  supovia

  Fetch safe metadata for one website owned by the authenticated Supovia organization. Organization ids, agent prompts, credentials, integration configuration, and arbitrary metadata are never returned.

  Connector

• dcl_evaluate_wallet

  DCL Trust Oracle — AI/LLM Output Audit (x402 MCP)

  POST-ACTION Wallet Secret Guardian ($0.02). Scans for BIP-39 seed phrases (12 or 24 consecutive wordlist words), raw hex or WIF-format private keys, Ethereum/Bitcoin wallet addresses, and API keys/bearer tokens appearing near wallet/custody/signing terminology. Any finding results in NO_COMMIT — wallet secrets have no safe threshold, unlike other DCL evaluators. Returns a `sanitized_output` with all matches redacted (null if nothing was found) and a masked `redacted_sample` per finding — the real value is never returned or stored server-side.

  Connector

• adcritter_get_design_guide

  AdCritter for Builders

  Returns AdCritter design guidance for an entity at a caller-chosen guidance level - screen experiences, API integration patterns, and design philosophy. The default ('full') returns step-by-step prescription (exact layouts, colors, copy text, column orders). Request 'patterns' for balanced hints including common design patterns with softened vocabulary. Request 'facts' if you have strong visual-design instincts and just want API integration bindings (or call adcritter_get_api_reference and adcritter_get_usage_guide directly and skip this tool). Guidance is format-agnostic - it describes outcomes and integration, never prescribes frameworks or architecture. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, geo, media-asset, plan, report, settings.

  Connector

• cyanheads_describe_entry

  cyanheads-mcp-server

  Return the description and install snippets for a named tool or server. For tools: the description and the server it belongs to. For servers: local (stdio, via npx) install snippets for every published server, plus remote (HTTP) connection snippets when a hosted endpoint exists — for every supported client, or one client via the client parameter.

  Connector

• avizo_docs

  avizo-mcp

  Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.

  Connector

• triage_ai_opportunity

  Sophon Consulting

  Score one proposed AI workflow across bottleneck severity, value capture, integration readiness, and risk posture. Returns a deterministic go-deeper or hold recommendation and a handoff-ready Markdown artifact. Read-only; not for organization-wide readiness reviews or production rollout planning.

  Connector

• list_skills

  mcp

  START HERE for any open-ended request. Lists the task playbooks this server supports — systematic learning from bookmarks, organising into themes, cleaning up, X-list intelligence, exporting data out, finding a half-remembered save, digests, and diagnosing sync. Each names when to use it; call get_skill for the exact tool sequence.

  Connector

• check_wellknown_discovery

  Agentic Commerce Tools

  Audit any website's agent-discovery surface in one call (free, via tools.agiscorecard.com). Checks the six files the agentic web uses to find and describe a business: /.well-known/ai-catalog.json (Agentic Resource Discovery manifest), /.well-known/mcp/server-card.json (MCP Server Card), /.well-known/agent-card.json (A2A Agent Card), /llms.txt, /agents.md, and robots.txt AI-crawler access (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot & co.). Returns a 0-100 discoverability score, per-file pass/warn/fail status with JSON validity checks, and a free generator link for every missing file. Use it to audit a merchant or SaaS site before agent integration, compare competitors' agent readiness, or produce a fix list. Complements agent_readiness_scan (page-level signals) with the well-known discovery layer. Free tier: please self-limit to a few calls per minute. High-volume / production agent use: pay-per-call APIs via the x402 payment protocol at https://x402.agiscorecard.com ($0.005 per call in USDC on Base — no account, no API key).

  Connector