312,396 tools. Last updated 2026-07-28 10:01
"Gin" matching MCP tools:
- Lodge a request-for-quotation with GreenCore Solutions Corp. A human reviews and answers every ticket — no order is decided by this tool. Returns a ticket ID for polling via check_rfq_status. Optionally reference a GTIN resolved on mcp.cpgknowledgegraph.ai and an SM-ECO-10060 market code.Connector
- Poll a ticket previously lodged on this MCP (RFQ, terms request, or escalation). Returns current status and, once a human has answered, the answer.Connector
- Ask a commercial or procedural question — terms, conditions, eligibility context, process. The question is lodged as a ticket and a human answers it. Returns a ticket ID for polling via check_rfq_status.Connector
- Hand a matter that cannot be resolved deterministically to GSC Navigator human review. Emits ACM-451 ESCALATE. Returns a ticket ID for polling via check_rfq_status.Connector
- Perform a software package vulnerability audit using SecDB. ## What this tool does Analyzes a list of software packages identified by PURL (Package URL) and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided. ## When to use this tool Use this tool when the user wants to determine: - whether application dependencies contain known vulnerabilities - whether a project is affected by security advisories - which packages require patching or upgrading ## Supported ecosystems - **npm** - Node.js packages (e.g. pkg:npm/lodash@4.17.21) - **maven** - Java/JVM packages (e.g. pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1) - **pypi** - Python packages (e.g. pkg:pypi/django@4.2.0) - **gem** - Ruby gems (e.g. pkg:gem/rails@7.0.0) - **cargo** - Rust crates (e.g. pkg:cargo/openssl-src@111.10) - **nuget** - .NET packages (e.g. pkg:nuget/Newtonsoft.Json@13.0.1) - **golang** - Go modules (e.g. pkg:golang/github.com/gin-gonic/gin@1.9.1) - **composer** - PHP packages (e.g. pkg:composer/symfony/symfony@6.4.0) ## Inputs - **purls**: list of Package URLs, one per entry. Generate them from your project manifest files: - Node.js: package.json / package-lock.json - Python: requirements.txt / Pipfile.lock / pyproject.toml - Ruby: Gemfile.lock - Go: go.mod / go.sum - Rust: Cargo.lock - PHP: composer.lock - Java: pom.xml / build.gradle - .NET: *.csproj / packages.lock.json ## Outputs - **report**: structured JSON objects describing the advisories affecting the audited packages. - **summary**: Markdown summary including total vulnerabilities, severity breakdown, and key findings. ## LLM usage guidelines - Never guess whether a package is vulnerable — always call this tool. - Only submit PURLs from the supported ecosystems listed above; others will be ignored. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.Connector
- Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01)Connector
Matching MCP Servers
- AlicenseAqualityAmaintenanceAbout The fast, idiomatic way to build MCP servers in Go. Gin-like DX with struct-tag auto schema, middleware, adapters for Gin/OpenAPI/gRPC.Last updated514Apache 2.0
- AlicenseAqualityAmaintenancePersistent long-term memory for AI coding assistants. Local SQLite, no cloud - 16 MCP tools to store, search, relate, and consolidate typed memories with a confidence lifecycle, hybrid BM25 + semantic search, namespaces, a knowledge graph, and a built-in OS keychain credential vault.Last updated164MIT
Matching MCP Connectors
Deterministic AI agent microtools, no accounts/API keys. fetch_extract: 98% token cut. 38 tools.
Real, calibrated Dota 2, Deadlock & Marvel Rivals win predictions, tier lists & counters.
- Full notable-person profile JSON by slug. Use for bio, timeline, and metadata without similar people or life-in-days context. Example slug: taylor-swift. ($0.02)Connector
- Knowledge pack: profile + life-in-days + similar people + birthday peers (+ quality / upgrade hint). Timeline events include day_number. Best starting point for agent context. Example slug: albert-einstein. ($0.05)Connector
- S-tier guaranteed pack (score≥85, timeline≥8, image, embedding). Errors if below bar. Use when you need high-quality, complete notable context. Example slug: elon-musk. ($0.10)Connector
- Get the authenticated user's current life context — identity, today's events, mood, inner circle, and social edges. Prefer get_context_pack for a full session bootstrap. Requires API key. ($0.15; API key required)Connector
- Life Context Protocol (LCP) reference pack for a Dayze user: identity + who matters (edges) + week calendar + semantic/recent memories. Includes protocol.version. Optional query focuses memories. Requires API key or share token. Spec: https://dayze.com/docs/life-context ($0.20; API key required)Connector
- Life-graph export: people nodes + person_connections edges. Optional event–people links. Requires API key. ($0.25; API key required)Connector
- Subgraph around one person_id — profile plus all declared connections. Requires API key. ($0.15; API key required)Connector
- User calendar events (range: today|week|month|year|decade). Requires API key. ($0.10; API key required)Connector
- List user CRM people (flat list). Each row includes contact_origin (personal|online|imported). Requires API key. ($0.10; API key required)Connector
- User memories from Dayze Agent. Pass query for semantic retrieval; omit for recent chronological. Requires API key. ($0.10; API key required)Connector
- List user expenses / cashflow summary. Requires API key. ($0.10; API key required)Connector
- List user trackers / habits / streaks. Requires API key. ($0.10; API key required)Connector
- Semantic search across the authenticated user life graph (events, people, memories). Requires API key. ($0.15; API key required)Connector
- Opens the interactive portfolio, optionally at a specific section. The user can also navigate between sections using tabs inside the portfolio. To jump to a specific section (e.g. the user asks for contact info or work samples), call this again with the section argument — the newest card supersedes older ones. The card's visual appearance (theme, colors, layout) is set by the portfolio owner and cannot be changed via this tool.Connector