启信宝 Apiservice MCP

Created By
qixina year ago
启信宝 MCP 是基于启信开放平台现有接口,赋能 AI 大模型快速获取启信开放平台所有API接口数据,在此基础上开展进一步分析处理,通过快速、安全、精准获取并处理企业数据,打通从数据获取到智能决策的“最后一公里”。
Overview

what is Qixin Apiservice?

Qixin Apiservice is a powerful tool that leverages the Qixin Open Platform's APIs to enable AI models to quickly access and analyze enterprise data, facilitating intelligent decision-making.

how to use Qixin Apiservice?

To use Qixin Apiservice, install it via npm or npx, and set your Qixin API credentials as environment variables before running the service.

key features of Qixin Apiservice?

  • Comprehensive enterprise search with fuzzy matching
  • Detailed enterprise information retrieval including ownership and management data
  • Multi-dimensional risk analysis
  • Access to executive information and legal data

use cases of Qixin Apiservice?

  1. Conducting thorough background checks on companies
  2. Assessing potential business risks before partnerships
  3. Analyzing executive backgrounds for investment decisions

FAQ from Qixin Apiservice?

  • How can I obtain a Qixin API key?

You can register on the Qixin Open Platform to get your API key.

  • Is there a cost associated with using Qixin Apiservice?

The service is free to use, but may have limitations based on API usage.

  • What types of data can I access?

You can access a wide range of data including company registration details, risk assessments, and executive information.

Server Config

{
  "mcpServers": {
    "qixin-apiservice": {
      "command": "npx",
      "args": [
        "@qixin-api/apiservice-mcp"
      ],
      "env": {
        "QIXIN_APP_KEY": "your_app_key_here",
        "QIXIN_SECRET_KEY": "your_secret_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qixin
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago