get_fibre_network_status — blobpedia MCP Tool Read-only
get_fibre_network_status
(get fibre network status) is one of 67 tools on the
blobpedia
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_fibre_network_status from your client
- Claude Code blobpedia get_fibre_network_status run in your project directory
- Claude Desktop blobpedia get_fibre_network_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor blobpedia get_fibre_network_status ~/.cursor/mcp.json
- VS Code blobpedia get_fibre_network_status .vscode/mcp.json
- Zed blobpedia get_fibre_network_status ~/.config/zed/settings.json
- Windsurf blobpedia get_fibre_network_status ~/.codeium/windsurf/mcp_config.json
- Cline blobpedia get_fibre_network_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI blobpedia get_fibre_network_status ~/.gemini/settings.json
- Grok blobpedia get_fibre_network_status .mcp.json (in your project root)
- ChatGPT blobpedia get_fibre_network_status Settings → Connectors → Advanced → Developer mode
- Claude.ai blobpedia get_fibre_network_status Settings → Connectors → Add custom connector
- LangChain blobpedia get_fibre_network_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http blobpedia https://blobpedia.org/mcpOther tools on this server
- search
- get_cip
- list_cips
- get_discussion
- get_whitepaper
- list_whitepapers
- get_trending
- get_doc
- get_cip_history
- get_cip_attachments
- get_cip_mentions
- get_recent_changes
- get_network_stats
- get_network_state
- list_ecosystem_projects
- list_datacenter_offers
- get_datacenter_offer
- list_datacenter_providers
- size_fibre_node
- list_celestia_validators
- get_celestia_validator
- get_celestia_network_health
- get_celestia_upgrade_status
- get_celestia_economics
- get_celestia_hardware_usage
- get_celestia_decentralization
- get_celestia_validator_guide
- list_celestia_resources
- get_celestia_operator_toolkit
- list_fibre_validators
- get_fibre_validator
- get_fibre_blob_market
- list_fibre_blobs
- get_fibre_blob
- list_fibre_events
- search_fibre
- list_repos
- list_github_discussions
- get_github_discussion
- get_video
- list_videos
- get_foundation_info
- semantic_search
- get_started_guide
- search_github_issues
- search_talks
- search_release_notes
- get_operator_upgrade_notes
- find_security_patches
- find_maintainer_guidance
- get_issue_status
- find_code_examples
- find_expert
- ecosystem_dependency_graph
- find_collaboration_opportunities
- diagnose_error
- get_breaking_changes
- detect_cip_dependency_chain
- get_sdk_changelog
- find_known_issues
- find_cip_for_feature
- get_latest_release
- get_radar
- find_similar_projects
- detect_drift
- learning_path
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.