← Registry

Developer Tools

bliplogger.com

Provides access to BlipLogger configuration and documentation, including installation protocols, API boundaries, and project summaries.

1 endpoint11 known toolsFirst detected July 19, 2026Last detected August 28, 2026

ENDPOINT 1

https://www.bliplogger.com/api/mcp

No auth detected

MCP server metadata

Name
bliplogger
Version
7K-ai-setup-readiness
Capabilities
toolsresourcesprompts

Known tools 11

read_ai_install_protocol

Returns the BlipLogger AI install protocol: the 12-point agent protocol, installation steps, human approval definition, and what requires explicit human approval.

Inferred read-only
read_machine_api_boundaries

Returns the BlipLogger Machine API boundaries: what the API accepts (draft entries only), required headers, payload limits, and what not to infer about BlipLogger capabilities.

Inferred read-only
read_widget_snippet

Returns the canonical and side-panel BlipLogger widget script tags and a post-install verification checklist.

Potential side effects
get_governance_boundary_summary

Returns a summary of what is and is not possible via BlipLogger MCP: human approval requirements, what is not live today, and permanently blocked capabilities.

Inferred read-only
get_project_summary

Returns a summary of the authenticated BlipLogger project: name, slug, visibility, creation date, and entry counts by status.

Inferred read-only
list_changelog_entries

Returns a paginated list of changelog entries for the authenticated BlipLogger project.

Inferred read-only
create_changelog_draft

Creates a governed draft changelog entry for the authenticated BlipLogger project.

Inferred read-only
get_project_install_context

Returns the complete install context for the authenticated BlipLogger project: project id, name, slug, canonical widget snippet with the real project slug, side-panel snippet, MCP endpoint, current authenticated tool list with required scopes, and human approval/governance boundaries.

Inferred read-only
validate_widget_install_snippet

Validates a submitted widget snippet or page HTML against the authorized BlipLogger project slug.

Inferred read-only
get_project_widget_runtime_status

Reports the BlipLogger-owned widget runtime status for the authorized project.

Inferred read-only
get_project_ai_setup_readiness

Reports AI setup readiness for the authorized BlipLogger project: project setup status, available MCP workflows with required scopes, current key capabilities, widget/runtime readiness summary, safe next steps, and hard boundaries.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bliplogger]
url = "https://www.bliplogger.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "bliplogger": {
      "type": "http",
      "url": "https://www.bliplogger.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: bliplogger
Remote MCP URL: https://www.bliplogger.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bliplogger": {
      "url": "https://www.bliplogger.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "bliplogger": {
      "type": "http",
      "url": "https://www.bliplogger.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "bliplogger",
  "transport": "streamable-http",
  "url": "https://www.bliplogger.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for bliplogger.com was fetched 2026-07-26T06:53:06.031Z and is being refreshed.

Trust status Neutral

bliplogger.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.