Publisher portfolio
petrovicistefan
Explore the MCP servers published by petrovicistefan, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 7
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 0
Active servers with a recorded connection probe
- Latest probe connected
- 0
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 7
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
io.github.petrovicistefan/mcp-dealfinder Search affiliate product feeds from any network and return tracked buy links with a disclosure. | Not measured | Not measured | 4 / 6 | Not checked yet |
MCP API Guardian Local OpenAPI contract and breaking-change checks for AI agents. | Not measured | Not measured | 4 / 6 | Not checked yet |
MCP Cost Optimizer Local-first LLM cost analysis and model-switch savings estimates for AI agents. | Not measured | Not measured | 4 / 6 | Not checked yet |
MCP Database Doctor Offline PostgreSQL query, migration and EXPLAIN diagnostics for AI agents. | Not measured | Not measured | 4 / 6 | Not checked yet |
MCP Dependency Doctor Read-only npm dependency diagnostics for AI coding agents. | Not measured | Not measured | 4 / 6 | Not checked yet |
MCP Security Guard Audit MCP servers for tool poisoning, rug pulls and supply-chain risk (OWASP MCP Top 10). | Not measured | Not measured | 4 / 6 | Not checked yet |
MCP SEO Auditor Read-only static SEO audits and bounded crawling for AI agents. | Not measured | Not measured | 4 / 6 | Not checked yet |
Company & identity
About petrovicistefan
petrovicistefan publishes MCP servers under the io.github.petrovicistefan namespace. This namespace is associated with a GitHub login in the MCP Registry.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.