msp-portfolio

endpoint

https://msp-portfolio.mansio-dev.workers.dev/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is msp-portfolio live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is msp-portfolio free to use?

Yes — the hub reached it with no key and no payment.

What tools does msp-portfolio have?

18 tools: search_projects, verify_repo, verify_article, verify_package, analyze_stack, get_issue_detail, verify_claim, simulate_architecture, ….

Is msp-portfolio safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_known_issues reads open 3h ago

  Get the owner's known-issues board — open debt with status, temperature (stable/watching) and deadlines. Use it to answer 'what's still broken' or 'what are you working on'. Read-only, closed world.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_timeline reads open 6h ago

  Get the engineering decision timeline.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_experiments reads open 6h ago

  Get the owner's engineering experiments — hypothesis, command, raw result and verdict (confirmed/refuted/partial) for each. Use it to answer 'what did you measure' or 'show me an experiment you ran'. Includes negative results (approaches that failed). Read-only, closed world.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_projects reads open 10h ago

  Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "filter": {
        "enum": [
          "all",
          "python",
          "typescript",
          "mcp",
          "aws",
          "ai"
        ],
        "type": "string",
        "description": "Filter projects by stack tag."
      }
    },
    "additionalProperties": {}
  }

  arguments 19 lines copy
• get_engineering_principles reads open 6h ago

  Get engineering principles with real examples and A/B-style counterfactuals.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_articles reads open 16h ago

  Get recent Dev.to articles with reading time, tags and links.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_antipatterns reads open 16h ago

  Get the owner's antipattern museum — real engineering mistakes with why they were bad, how they were fixed, and the lesson. Read-only, closed world.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_commit_history reads open 10h ago

  Get recent commit history across the owner's public repos. Reads the deployed snapshot and reports its `fetchedAt` and `ageMinutes`, so 'how current is this?' is answered by the payload instead of by trusting this description. Use it to answer 'what has he been building lately' or 'show the hardest bugs he has fixed'.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_diary reads open 10h ago

  Get the owner's engineering diary — incidents, root causes, fixes and guards, each tagged with a pattern (NEW vs recurring). Use it to answer 'what broke and how did you fix it' or 'show your hardest debugging session'. Read-only, closed world.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• get_profile reads open 16h ago

  Get the owner's professional profile summary, plus nextSteps — concrete ways to continue (contact channels, GitHub, MCP connect). Use it as the first tool in an interview.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {},
    "additionalProperties": {}
  }

  arguments 6 lines copy
• search_projects reads unknown 40h ago

  Free-text search across portfolio projects — name, tagline, description, stack and decision-log rationale. Returns matched projects with a score and the fields that matched. Use when a fixed stack-tag filter is too narrow (e.g. 'RAG', 'latency', 'Zed'). Read-only, closed world.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Search terms, e.g. 'RAG' or 'latency Zed'."
      }
    },
    "additionalProperties": {}
  }

  arguments 14 lines copy
• verify_repo reads unknown 3h ago

  Verify a GitHub repository against the primary source: fetches the actual repo metadata (exists, language, description, topics, stars, last push) from the GitHub API and cross-checks it with the portfolio's project record when the repo is one of the owner's projects (language/stack agreement). With readme:true it also returns the actual README text, so claims about what the project does can be checked against the repository's own words. Use it to ground claims like 'the repo is Python' or 'he maintains mscodebase-intelligence' with live data instead of trusting the claim. Read-only, open world (network fetch).

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "repo"
    ],
    "properties": {
      "repo": {
        "type": "string",
        "description": "Repository name, e.g. \"mscodebase-intelligence\" (owner defaults to ManSio) or full \"owner/name\" or a github.com URL."
      },
      "readme": {
        "type": "boolean",
        "description": "Also fetch the repository README (first ~1200 chars) for claim checks against the project's own description."
      }
    },
    "additionalProperties": {}
  }

  arguments 18 lines copy
• verify_article reads unknown 32h ago

  Verify an article against the primary source (Dev.to): does the owner have a published article matching the query? Fetches the live Dev.to API for the owner's articles and returns the real title/date/reactions/url when found — or an honest 'not found'. Use it to ground claims like 'he wrote about agent memory' in the platform's data instead of the portfolio's own words. Read-only, open world (network fetch).

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Article title fragment or keyword, e.g. \"agent memory\" or an exact title."
      }
    },
    "additionalProperties": {}
  }

  arguments 14 lines copy
• verify_package reads unknown 32h ago

  Verify an npm package against the primary source (registry.npmjs.org): does it exist, latest version, publish date, description, license, maintainers — and is the owner among them? Use it to ground claims like 'he published an npm package' in the registry's data instead of the portfolio's. Honest 'not found' when the package does not exist. Read-only, open world (network fetch).

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "package"
    ],
    "properties": {
      "package": {
        "type": "string",
        "description": "npm package name, e.g. \"msp-portfolio\" (lowercase)."
      }
    },
    "additionalProperties": {}
  }

  arguments 14 lines copy
• analyze_stack reads unknown 3h ago

  Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "required_skills"
    ],
    "properties": {
      "required_skills": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Skills the job requires."
      }
    },
    "additionalProperties": {}
  }

  arguments 17 lines copy
• get_issue_detail reads unknown 40h ago

  Get the full detail of a single known issue by its ID (e.g. 'KI-109'). Drills into one open problem: status, temperature, owner, linked source and the raw problem statement. Returns a clear not-found with the available IDs if the ID does not match. Read-only, closed world.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The issue ID, e.g. 'KI-109' (case-insensitive)."
      }
    },
    "additionalProperties": {}
  }

  arguments 14 lines copy
• verify_claim reads unknown never probed

  Ground a claim about the owner against the portfolio's data (profile, projects, principles, timeline, antipatterns, experiments, diary, known issues). Deterministic: returns the evidence records that support the claim (with source paths) and a supported verdict. Use it before asserting a fact about the owner, or to check what an answer was based on.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "claim"
    ],
    "properties": {
      "claim": {
        "type": "string",
        "description": "The claim to verify, e.g. \"built an MCP server with LanceDB hybrid search\"."
      }
    },
    "additionalProperties": {}
  }

  arguments 14 lines copy
• simulate_architecture reads unknown 40h ago

  Simulate how a project's architecture behaves under a scenario (load spike, node loss, cache cold, LLM saturation). Returns latency percentiles per load and bottleneck analysis.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "project_id",
      "scenario"
    ],
    "properties": {
      "scenario": {
        "enum": [
          "load_spike",
          "node_loss",
          "cache_cold",
          "llm_saturation"
        ],
        "type": "string",
        "description": "Scenario to apply."
      },
      "project_id": {
        "enum": [
          "mscodebase-intelligence",
          "gemma_agent",
          "msp-portfolio"
        ],
        "type": "string",
        "description": "Project to simulate."
      }
    },
    "additionalProperties": {}
  }

  arguments 30 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.