pulsemcp verified Safe content atomic mcp-remote

Semantic Context

This semantic code search MCP server by Damian Pramparo provides enterprise-grade vector database integration for indexing and searching codebases using ChromaDB for storage and either OpenAI or Ollama for embeddings. Built with TypeScript and featuring both stdio and HTTP server modes, it offers tools for indexing local project directories with configurable file patterns, performing semantic code searches across indexed repositories, and retrieving file contents with metadata tracking including project names, file types, and chunk indexing. The implementation includes Docker Compose setup with ChromaDB, Ollama, Redis, and PostgreSQL services, comprehensive file type support covering 50+ programming languages and formats, and streaming file processing for handling large codebases efficiently, making it ideal for development teams building AI-powered code search systems, enterprise knowledge bases, and developer productivity tools that need to understand and navigate large codebases semantically.

Cognium trust score

95%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/damian-pramparo/semantic-context-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Semantic Context from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"