How do I find my ShangQian Developer ID and Secret?

Log in to the [BestSign Developer Platform](https://open.bestsign.cn/), navigate to the 'Application Management' or 'Credentials' section to find your unique Developer ID and RT Secret.

What is the 'account' identifier?

The account identifier is a unique string used to identify a user in the ShangQian system, typically a mobile phone number or an email address. It is required for registration and signing operations.

Does this server handle HMAC-SHA1 signatures?

Yes! The server automatically calculates the required HMAC-SHA1 signature using your RT Secret for every request, ensuring secure authorized communication with the ShangQian API.

ShangQian / 上上签 (BestSign) MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: ShangQian / 上上签 (BestSign)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to ShangQian / 上上签 (BestSign) through Vinkius, pass the Edge URL in the `mcps` parameter and every ShangQian / 上上签 (BestSign) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="ShangQian / 上上签 (BestSign) Specialist",
    goal="Help users interact with ShangQian / 上上签 (BestSign) effectively",
    backstory=(
        "You are an expert at leveraging ShangQian / 上上签 (BestSign) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in ShangQian / 上上签 (BestSign) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About ShangQian / 上上签 (BestSign) MCP Server

Empower your AI agent to orchestrate your digital document workflows and electronic signatures with ShangQian (BestSign / 上上签), the premier B2B digital signature platform in China. By connecting ShangQian to your agent, you transform complex contract lifecycle management, user identity verification (KYC), and signature orchestration into a natural conversation. Your agent can instantly register new personal or enterprise users, initialize contracts from pre-defined templates, retrieve detailed contract statuses, and even generate secure download links for executed documents without you ever needing to navigate the comprehensive BestSign Management Portal. Whether you are automating HR onboarding or coordinating high-volume commercial agreements, your agent acts as a real-time contract coordinator, providing accurate and fast results from a single, authorized source.

When paired with CrewAI, ShangQian / 上上签 (BestSign) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ShangQian / 上上签 (BestSign) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

User Orchestration — Register new users, verify digital certificates, and perform KYC identity checks.
Contract Management — Create signature-ready contracts using templates and monitor real-time completion status.
Template Automation — List and audit your library of contract templates and upload new document definitions.
Execution Control — Trigger signature operations for authorized accounts and retrieve finalized PDF documents.
Operational Monitoring — Verify API connectivity and monitor system health to ensure signature reliability.

The ShangQian / 上上签 (BestSign) MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect ShangQian / 上上签 (BestSign) to CrewAI via MCP

Follow these steps to integrate the ShangQian / 上上签 (BestSign) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from ShangQian / 上上签 (BestSign)

Why Use CrewAI with the ShangQian / 上上签 (BestSign) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ShangQian / 上上签 (BestSign) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

ShangQian / 上上签 (BestSign) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the ShangQian / 上上签 (BestSign) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries ShangQian / 上上签 (BestSign) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries ShangQian / 上上签 (BestSign), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain ShangQian / 上上签 (BestSign) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries ShangQian / 上上签 (BestSign) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

ShangQian / 上上签 (BestSign) MCP Tools for CrewAI (8)

These 8 tools become available when you connect ShangQian / 上上签 (BestSign) to CrewAI via MCP:

create_shangqian_contract

Create signature contract

get_contract_details

Get contract metadata

get_contract_download

Get download URL

get_user_certificate

Get user certificate

register_shangqian_user

sign_contract_now

Sign contract

upload_shangqian_template

Upload new template

verify_identity_v2

Verify user identity

Example Prompts for ShangQian / 上上签 (BestSign) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with ShangQian / 上上签 (BestSign) immediately.

"List all contract templates in my ShangQian account."

"Register a new enterprise user 'Vinkius' with account 'vinkius@example.com'."

"What is the status of contract '88210934'?"

Troubleshooting ShangQian / 上上签 (BestSign) MCP Server with CrewAI

Common issues when connecting ShangQian / 上上签 (BestSign) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

ShangQian / 上上签 (BestSign) + CrewAI FAQ

Common questions about integrating ShangQian / 上上签 (BestSign) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.