"Information about OBS (Open Broadcaster Software)" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Per-harness pre-open verdict on a received repo's agent-control surface.
**Can AI actually read your page?** ChatGPT, Perplexity, Claude and Google's AI Overviews fetch pages very differently from your browser — no JavaScript, tight timeouts, and a robots.txt rulebook of their own. Lekta fetches a URL exactly the way they do and grades what survives, **A+ to F**. This is the technical half of **AEO** (answer engine optimization) and **GEO** (generative engine optimization): before a model can cite you, it has to be able to fetch you, parse you, and find one sentence worth quoting. **The loop this server was built for:** `Audit https://mysite.com/pricing with Lekta, apply the fixes it lists, audit it again, and show me the difference.` Your agent gets a graded verdict, a ranked fix plan with the exact markup to paste, and a diff that proves the change landed. Repeat until A+. **Four layers, 100 points:** **Access** 25 — do the ~17 AI crawler tokens get past robots.txt? **Indexability** 25 — how much content survives without JavaScript? **Answerability** 30 — is there a single quotable sentence an engine can lift? **Recency** 20 — can a model tell when this page was last true? **What this is not:** a rank tracker. Lekta will not tell you how often ChatGPT mentions your brand. It tells you whether your page can be read and quoted when it does — the part you can actually fix. **No black box.** Every finding cites its basis — an RFC, a vendor doc, or a dated measurement we ran. The engine is versioned with a public changelog: a score never moves without a published shift table. **Tools:** `lekta_audit` (fresh fetch) · `lekta_report` (cached read) · `lekta_fix_plan` (ranked, paste-ready) · `lekta_diff` (before/after) · `lekta_my_sites` Listing tools is open. Tool calls need a free key from lekta.dev/en/panel/api — send `Authorization: Bearer lekta_…` or `x-api-key`. Cached reads, fix plans and diffs cost nothing; only fresh fetches count against the daily limit. **Topics:** AEO · GEO · AI SEO · LLM SEO · answer engine optimization · generative engine optimization · AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) · JavaScript-free indexability · structured data · content freshness
Hosted, OAuth-gated endpoint for quantakrypto's post-quantum crypto tools: scan code for quantum-vulnerable cryptography (RSA/ECDH/ECDSA/DH) and get NIST ML-KEM/ML-DSA/SLH-DSA migration guidance over authenticated HTTP — nothing to install. Sign-in required (Google/GitHub/email). Same tools as the open-source @quantakrypto/mcp server; source at github.com/quantakrypto/pqc-tools.
Known open GitHub issues in exact npm and PyPI versions, with workarounds, for coding agents.
Bounded software search, unknown requirements, and the origins of project identifiers.
Open-source licence risk checks for AI coding agents and dependency trees.
The OpenZeppelin Stylus Contracts MCP server generates secure smart contracts for the Arbitrum Stylus environment using OpenZeppelin templates, including ERC-20, ERC-721, and ERC-1155 standards. It automatically validates generated code against OpenZeppelin's security and style rules, enforcing best practices for imports, modifiers, naming conventions, and security checks to prevent common vulnerabilities. The server integrates with AI development tools like Cursor, Claude, Gemini, Windsurf, and VS Code to enable AI-assisted, production-ready smart contract development.
The OpenZeppelin Solidity Contracts MCP server integrates OpenZeppelin's security and style rules into AI-driven development workflows, enabling AI assistants to generate safe, correct, and production-ready smart contracts. It automatically validates generated code against OpenZeppelin standards (including imports, modifiers, naming conventions, and security checks) and supports various contract types including ERC-20, ERC-721, ERC-1155, Stablecoins, RWA, Governor, and Account contracts through prompt-driven workflows.
The OpenZeppelin Cairo Contracts MCP server generates secure smart contracts in the Cairo language for Starknet environments based on OpenZeppelin templates. It brings OpenZeppelin's proven security and style rules directly into AI-driven development workflows to create safe, production-ready contracts. Key capabilities include providing templates for ERC-20, ERC-721, ERC-1155, Multisig, Governor, and Vesting contracts.
Commit-pace and release probabilities for open-source repositories. Docs: anteproof.com/docs
Software Heritage MCP.
GitHub project health, package dependency risk, trending repos, license & package comparison.
Software supply chain security: SBOMs, vulnerabilities, fixes, policies and compliance data.
Tell your assistant you're about to launch. It checks the app your builder synced to GitHub, tells you what would break for real users, hands you the fix, and re-checks after the sync. Point it at any public repo first (nothing to install, nothing to grant) and see exactly what comes back before you connect the one that matters.
Security checks for apps built with AI: leaked keys, open routes, database rules, each with a fix.
Build Laravel apps through conversation. Code stored as structured JSON for surgical AI edits.
Permission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role.
Monitor third-party API changes in GitHub repos, map breaks to files, open reviewable auto-fix PRs.
Software component catalog: search your org's services, docs, APIs, dependencies, and ownership.
Review connected software projects, submit local findings and read reports with explicit approval.
